This README describes GNU Stow. This is not the definitive documentation for Stow; for that, see the info manual.
Stow is a symlink farm manager program which takes distinct sets of software and/or data located in separate directories on the filesystem, and makes them all appear to be installed in a single directory tree.
Originally Stow was born to address the need to administer, upgrade,
install, and remove files in independent software packages without
confusing them with other files sharing the same file system space.
For instance, many years ago it used to be common to compile programs
such as Perl and Emacs from source and install them in /usr/local.
By using Stow, /usr/local/bin could contain symlinks to files within
/usr/local/stow/emacs/bin, /usr/local/stow/perl/bin etc., and
likewise recursively for any other subdirectories such as .../share,
.../man, and so on.
While this is useful for keeping track of system-wide and per-user
installations of software built from source, in more recent times
software packages are often managed by more sophisticated package
management software such as
rpm,
dpkg, and
Nix / GNU
Guix, or language-native
package managers such as Ruby's
gem, Python's
pip,
Javascript's npm,
and so on.
However Stow is still used not only for software package management, but also for other purposes, such as facilitating a more controlled approach to management of configuration files in the user's home directory, especially when coupled with version control systems.
Stow was inspired by Carnegie Mellon's Depot program, but is
substantially simpler and safer. Whereas Depot required database files
to keep things in sync, Stow stores no extra state between runs, so
there's no danger (as there was in Depot) of mangling directories when
file hierarchies don't match the database. Also unlike Depot, Stow will
never delete any files, directories, or links that appear in a Stow
directory (e.g., /usr/local/stow/emacs), so it's always possible
to rebuild the target tree (e.g., /usr/local).
Stow is implemented as a combination of a Perl script providing a CLI interface, and a backend Perl module which does most of the work.
You can get the latest information about Stow from the home page:
http://www.gnu.org/software/stow/
See INSTALL.md for installation instructions.
Documentation for Stow is available
online, as is
documentation for most GNU
software. Once you have Stow
installed, you may also find more information about Stow by running
info stow or man stow, or by looking at /usr/share/doc/stow/,
/usr/local/doc/stow/, or similar directories on your system. A
brief summary is available by running stow --help.
Stow has the following mailing lists:
- help-stow is for general user help and discussion.
- stow-devel is used to discuss most aspects of Stow, including development and enhancement requests.
- bug-stow is for bug reports.
Announcements about Stow are posted to info-stow and also, as with most other GNU software, to info-gnu (archive).
Security reports that should not be made immediately public can be sent directly to the maintainer. If there is no response to an urgent issue, you can escalate to the general security mailing list for advice.
The Savannah project also has a mailing lists page.
Please see the CONTRIBUTING.md file.
Stow is free software, licensed under the GNU General Public License,
which can be found in the file COPYING.
Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. This file is offered as-is, without any warranty.
Stow was inspired by Carnegie Mellon's "Depot" program, but is
substantially simpler. Whereas Depot requires database files to keep
things in sync, Stow stores no extra state between runs, so there's no
danger (as there is in Depot) of mangling directories when file
hierarchies don't match the database. Also unlike Depot, Stow will
never delete any files, directories, or links that appear in a Stow
directory (e.g., /usr/local/stow/emacs), so it's always possible to
rebuild the target tree (e.g., /usr/local).
For a high-level overview of the contributions of the main developers
over the years, see the AUTHORS file.
For a more detailed history, please see the ChangeLog file.
