Add the appropriate version of the package into the project's package list and update your local packages.
You may install more than one package at once. If you want to install more than one package and want to use the latest version, you may use - instead of a version number.
If --fix is specified, all the dependencies will be added to etc/project-packages, otherwise we always get the latest version of all dependent packages. You must --fix the project file to store the versions of the dependencies. This is mostly important for rollback purposes, but it can be helpful to make sure two playpens are using the same versions even if they use different package-archives.
If --update is specified, only those packages which changed in the project-packages; will be installed; etc/project-packages will not modified.
If --no-update is specified, no packages will be built or installed at all; only etc/project-packages.
The default is --fix.
Downloads the latest ext/etc/package-archives/* files. This updates the playpen so that you can install or upgrade to the latest versions available in the package-archive.
Replace setup-env and bin/wigwam-bootstrap with the latest versions distributed with wigwam. (Normally these files are unaffected by upgrading your wigwam-base.)
This is separated from the upgrade of wigwam-base so that if you must make changes to wigwam-bootstrap or setup-env they will be preserved.
Build and install any needed packages to make the installed packages match the etc/project-packages file.
Upgrade packages to the latest versions, according to your local project_packages. This will install previously uninstalled packages too.
If no packages are specified, all packages in the project will be upgraded.
With --force, the package will be downloaded again from the package archive, rebuilt, and reinstalled, even if all these steps appear unnecessary.
Build or install the source code in src, in the standard way. See the Section called Building and Installing Binaries in a Project in Chapter 3. This can be convenient if you don't have a simple Makefile, but it's mostly for testing, since this is how the project's source code will be compiled on the live and staging servers.