News

• BLOCK_SIZE variable in pacorc was not properly recognized (thanks Kevin Williams).
• When appending files to a log, sizes of missing files were cleared.
• [pacoball] Archive symlinks to missing files too (thanks Sergei Butakov).
• [rpm2paco] Option -q caused the program to exit.

^top^

 Description

Paco 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.

Technically, this is done by preloading a shared library before installation using the environment variable LD_PRELOAD. During installation this library catches the system calls that cause filesystem alterations, logging the created files.

Like any other package manager, paco also provides several options to show package information in different formats. It can remove packages too, among some other basic operations. See the man page for more details.

Gpaco is the graphic interface of paco. It's included in the same tarball and installed by default, althought it can be disabled at configure time. Gpaco requires GTK+ (2.6 or later). As of version 2.0.0 gpaco requires also GTKMM (2.8 or later).
See some screenshots here.

Paco is protected by the GNU General Public License. Look at the COPYING file in the tarball for more details.

Note:
Paco does not work on systems in which the executables involved in the installation of the packages (mv, cp, install...) are statically linked against libc, like FreeBSD and OpenBSD.

^top^

 Links

Mailing list paco@freshmeat.net paco@SourceForge.net paco@GnomeFiles.org

^top^

 Authors

David Rosal, <shin@**> (where ** = tinet.cat), and contributors.