-
Notifications
You must be signed in to change notification settings - Fork 24
New coapp command line interface
The CoApp command line client has a simple, yet flexible interface.
When redirecting or piping the results of a CoApp command, the tool will suppress cosmetic formatting and simply list the results of the given command (very useful for chaining the results of one execution into another).
CoApp [options] <command> <parameters>
All commands are in the form verb-noun (similar to powershell cmdlets) and can be followed by zero or more parameters.
Any commands that takes parameters after the command will accept a list of packages on the command line or via stdin.
list-package <pkg-spec>...
get-packageinfo <pkg-spec>...
install-package <pkg-spec>...
remove-package <pkg-spec>...
update-package <pkg-spec>...
trim
activate-package <pkg-spec>...
block-package <pkg-spec>...
unblock-package <pkg-spec>...
mark-package <pkg-spec>...
unmark-package <pkg-spec>...
list-feed
add-feed <feed-location>...
remove-feed <feed-location>...
<pkg-spec>...
Packages have a canonical name (in the form packagename-##.##.##.##-arch-publickeytoken
) which uniquely identifies it apart from other packages. Commands expecting a package name will always take the full canonical name or alternatively, the user can provide a partial name and CoApp will attempt to determine what the user is requesting.
Generally there are three types of inputs that can be specified for the package:
- a canonical package name (or partial canonical name)
- a local path (to either a package file or a package directory for use as a package feed )
- a URL (to either a remote package file, or a package atom feed for use as a package feed )
<feed-location>...
Generally there are two types of inputs that can be specified for package feeds:
- a local path (to either a package file or a package directory for use as a package feed )
- a URL (to either a remote package file, or a package atom feed for use as a package feed )