Free no package gtk 2.0 found software for linux

autopackage allows developers to produce "install anywhere" packages for 3rd party Linux software. The resulting packages support both graphical and terminal frontends, support dependency checking and resolution, and use deep desktop integration.
Additionally, tools to enhance the packaged software such as binreloc and relaytool are provided. By providing an autopackage, developers can ensure their users always have an easy way of installing the latest release of their software.
autopackage is stable, tested software that has been deployed by high profile projects. It has a strong commitment to backwards compatibility: your packages will continue to install as we add new features, although you may need to recompile them to get the new functionality.
Version 1.0 can build, install, verify and uninstall fairly complex packages (mplayer, gaim, inkscape etc), and promises backwards compatibility from this point forward.
Autopackage can resolve dependencies either from local files or from remote servers. It currently has simple support for package updates. It does not support integration with the native package manager although these features are planned for after the 1.0 release.
Main features:
- Build packages that will install on many different distros
- Multiple front ends: best is automatically chosen so GUI users get a graphical front end, and command line users get a text based interface
- Multiple language support (both in tools and for your own packages)
- Automatically verifies and resolves dependencies no matter how the software was installed. This means you dont have to use autopackage for all your software, or even any of it, for packages to succesfully install.
Enhancements:
- KDE not finding the hidden .desktop that associates x-autopackage -> autopackage-launcher-gtk on Fedora Core 3/KDE 3.3 - change Category to Categories in autopackage-launcher-gtk.desktop
- Package did not install with apkg-installer after executing .package with -d function stripDupedItems was updated to pass unit test autopackage RPM requires autopackage-gtk RPM function safeSed mishandled language detection for in-place editing
- Two desktop files were being generated - not correctly detecting if the Gnome version installed supports XDG .desktop locations
- Working directories were not being deleted makepackage checks for sealed packages not being included

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.

GIMP Animation Package is a collection of Plug-Ins to extend the GIMP with capabilities to edit and create Animations as sequences of single frames.

Please note that gimp-gap 2.2.1 requires gimp 2.2 and glib 2.8 or higher. It is recommended to use gtk+ 2.8.

Additional Installation Notes:

This GIMP-GAP release includes sourcecode tarballs of external libraries :

- ffmpeg
- libmpeg3

Those libs are built automatically. Configuration options for those libs can be set by editing the
files:

extern_libs/configure_options_ffmpeg.txt
extern_libs/configure_options_libmpeg3.txt

Those configure_option files are read by the master .configure script

Installation:

./autogen.sh # includes the ./configure call
make
make install

GIMP is an acronym for GNU Image Manipulation Program. It is a freely distributed program for such tasks as photo retouching, image composition and image authoring.

Kpackage project is a KDE tool for installing, viewing and uninstalling packages.

The formats supported include RPM, Debian, Slackware and BSD package manager.

KPackage is part of the KDE project.

KPackage can be found in the kdeadmin package.

Acovea/GTK project is a GTK-based graphical front end for the Acovea (Analysis of Compiler Options via Evolutionary Algorithm) optimization engine.

The Acovea engine ships with a command-line driver named runacovea. I like command-line utilities, and probably spend as much time at the prompt as I do clicking buttons. Still, a graphical interface can provide a certain ease-of-use that is lacking in a command-line application.

PHP-GTK is a PHP extension that implements language bindings for GTK+ toolkit.

PHP-GTK is an extension for the PHP programming language that implements language bindings for GTK+. It provides an object-oriented interface to GTK+ classes and functions and greatly simplifies writing client-side cross-platform GUI applications.

Paco project is a source code package organizer for Unix/Linux systems, originally written to aid package management when installing an LFS system.
When installing a package from sources, paco wraps the "make install" command (or whatever is needed to install the files into the system), and generates a log containing the list of all installed files.
Like any other package manager, paco provides several options to print package information in different formats. It can also remove packages, among some other basic operations.
Technically, paco follows the same approach as CheckInstall: A library is preloaded before installation, and during installation it catches the system calls that cause filesystem alterations, logging the names of the created files.
But unlike CheckInstall, paco doesnt create rpm or dpkg packages. Paco is a stand-alone package manager. It can even install rpm, dpkg or slackware binary packages with the provided script superpaco.
Gpaco is the GTK+ graphic interface of paco. Its included in the same tarball and installed by default. Gpaco requires GTK+ (2.6 or later), and pkg-config.
Enhancements:
- Removed repeated text in the man page of paco (thanks Georg Grafendorfer).
- The option -x|--expand has been removed (though it is silently ignored for backwards compatibility). Now the command line package names are automatically expanded like in rpm(8), except when logging packages. In this case the package name must be introduced exactly.
- Do not search for the name of the package in config.log (thanks Mirco Lorenzoni).
- Fix a doubled DESTDIR bug in doc/Makefile (thanks Matthew Bruenig).
- Rewritten libpaco-log in C. This prevents a glibc installation failure when building LFS in chapter 6.
- Fixed bug that made paco log compressed files twice in some cases.
- Use RTLD_NEXT in libpaco-log. Fixes bug in some systems (thanks Roland Schatz).
- When logging installations, files in /proc are always excluded, regardless of the variable EXCLUDE in pacorc or the arguments to the option -E|--exclude.
- Better strip the release suffix in rpm2paco and superpaco.
- [gpaco] Fixed several problems in "Import RPM database".

The Smart Package Manager project has the ambitious objective of creating smart and portable algorithms for solving adequately the problem of managing software upgrading and installation.
This tool works in all major distributions, and will bring notable advantages over native tools currently in use (APT, APT-RPM, YUM, URPMI, etc).
Notice that this project is not a magical bridge between every distribution in the planet. Instead, this is a software offering better package management for these distributions, even when working with their own packages.
Using multiple package managers at the same time (like rpm and dpkg) is possible, even though not the software goal at this moment.
This project is in beta testing. Please, understand that bugs are expected to be found at that stage, and there are features that still must be implemented in the forthcoming future. Even then, this project is being tested in a considerable number of machines for several months already.
Enhancements:
- A channel --remove-all option was added.
- A bug that made the rpm-metadata loader ignore explicitly provided files in certain situations was fixed.
- A detectsys.py plugin was added, which will automatically detect and include system channels when theyre missing.
- Double conversion of paths in LocalMediaHandler is now avoided.
- German translations were integrated and the French translations were merged.
- The deb backend now uses an underline for the name/version separator.
- A bug in the protected read code for old Python versions was fixed along with a locking issue in the RPM pm