Installing Vesta with RedHat/Debian Vesta packages

Since release/12, we've provided install-able versions of Vesta for Linux systems using the RedHat package manager (rpm) and the Debian package manager (dpkg):

These packages make installing Vesta much simpler than the traditional by-hand method, but the "Getting Started with Vesta" guide is a more complete reference than this page.

Note that every installation needs at least one machine with the vesta-server package installed. Even if you don't expect to provide sources to others over a network, you need a Vesta repository to act as a peer to the public Vesta repository to try out Vesta.


After installing the packages, you should run /usr/sbin/ (part of the vesta-server package). This asks you some important questions to complete the configuration of your installation, starts the servers, and optionally replicates the sources for Vesta and some examples from the public Vesta repository.

Experienced users can feel free to edit the Vesta configuration file and the repository export file themselves, but we recommend that first-time installers use this script.

Filesystem Layout

In a system with Vesta installed from either the RedHat or Debian packages, there are some key files and directories you should be aware of:

Note that the filesystem layout in the install-able packages is different from what's suggested in the traditional by-hand installation. This was done to conform to the Filesystem Hierarchy Standard (FHS).

Multiple Clients

If you plan to have multiple client machines as part of the same Vesta installation, here's what you should do:

  1. Start by installing vesta-server and vesta-common on the server host.
  2. Make sure that the server and all clients have assigned hostnames, and that they can all resolve each others hostnames and use them to contact each other (e.g. with ping).
  3. Share user and group information between all the machines (e.g. using NIS or LDAP).
  4. Export /var/lib/vesta from the server machine and mount if on all the clients (e.g. using NFS).
  5. Install vesta-common on all the client machines.
  6. Add all the client hostnames to the "hosts" configuration variable in the appropriate platform sections (i.e. [Linux2.4-i386] for x86 Linux). This makes it possible for builds to run tools across multiple machines in parallel.

See Also

You'll probably find it useful to go through the tutorialThe vesta-intro man page is a useful guide to Vesta concepts and terminology.  The command summary is a helpful reference for the most common Vesta user tasks.

Be sure you understand how to use the weeder (or alternatively EraseCache and QuickWeed).  If you don't periodically use these tools to purge the results of old builds, they'll just accumulate in /var/lib/vesta.

For more resources to learn about Vesta, see the LearningVesta page at our wiki.

If You Run Into Trouble

Users of newer RedHat systems may get an error when trying to install about a missing dependency for libstdc++. The solution is to install the compat-libstdc++ RPM.

If you encounter any other problems, send e-mail to the vesta-users mailing list (<vesta dash users at lists dot sourceforge dot net>) for help.

Ken Schalk <ken at xorian dot net>
Last modified: Tue Jul 21 17:09:04 EDT 2009