PATH may be a
build.yml file or a directory. If a directory is given, Quilt will internally generate a build file (useful, e.g. for directories of images).
build.yml is for users who want fine-grained control over parsing.
Stores the package in the registry |
Installs a package or sub-package.
--force - skips yes/no prompt in the case of overwrite
--meta-only - install only the package metadata (useful for filtering large packages)
Installs all specified packages using the requirements syntax (above) |
Removes the package from the registry. Does not delete local data.
Display push history
Display versions of a package
Associate a version with a hash
List available tags
Associate a tag with a hash
Remove a tag
Authenticate to a registry
List user who have access to a package |
Grant read access to a user or group (one of
Remove read access
List installed packages
Remove a package from local storage (but not from the registry)
quilt search "SEARCH STRING" Search registry for packages by user or package name
Export data to current dir
Export data to specified destination
quilt export USER/PACKAGE [DEST] --force Overwrite files at destination
Export data with symbolic links to reduce disk footprint.
If a node references raw (file) data, symbolic links may be used instead of copying data when exporting.
When using any OS
If a file is edited, it may corrupt the local quilt repository. Preventing this is up to the user.
When using Windows
Symbolic links may not be supported
Symbolic links may require special permissions
Symbolic links may require administrative access (even if an administrator has the appropriate permissions)