anymods contain shell library modules and commands for any(1). The modules significantly extend functions of core engine, but with the price of relying on external programs. Each module is self-contained mini-source tarball, handled independently from others. Modular system helps to keep the engine tiny, use full-pledged build infrastructure, avoid the unneeded dependencies and quickly add new modules to overall set.

Module shell files reside in any/lib/ inside working dir. To use installed module, one needs to add according keyword to data id in command line or config file.
For example, usage of module trackcontent requires to add trackcontent to the first argument of anch do (any-do(1)):

        $ anch do id,trackcontent some-packs.src

So installed modules do not affect the behaviour of your working directory on their own.

Index of available modules is below. Not all of them will be available from working directory or anyinit(1) in case of selective installation.

builddep

gathers the build-time dependencies for new packages.

buildfresh

detects the list of packages to rebuild after sources have been updated.

fetchdevgit

handles the development sources with git(1).

fetchstatic

handles the source archives from remote hosts (scp(1)).

packdeb

creates binary packages in .deb format for dpkg(1).

packslack

creates binary packages in .txz format for pkgtools(1) from Slackware distribution.

trackcontent

does regression checks, comparing current package state with a previous one.

trackelf

checks ELF files on consistency.

any(1)