diff options
author | John S. Urban <urbanjost@comcast.net> | 2021-03-01 20:53:25 -0500 |
---|---|---|
committer | John S. Urban <urbanjost@comcast.net> | 2021-03-01 20:53:25 -0500 |
commit | ab57ec6b225edf848229e8f9f1cabecb6e508ade (patch) | |
tree | a18f01e4a93d5aa99a6faa3b832e6d0350765ab3 /test/help_test | |
parent | 90e1409f4e61899c8f1fb052888c794f3bcdb11e (diff) | |
download | fpm-ab57ec6b225edf848229e8f9f1cabecb6e508ade.tar.gz fpm-ab57ec6b225edf848229e8f9f1cabecb6e508ade.zip |
remove --add and add .
The default behavior becomes very similar to the Rust cargo(1)
package manager in that
# run application if there is one target
fpm run -- ARGS cargo run -- ARGS
fpm run NAME(S) cargo run --example NAME
fpm run --example NAME(S) cargo run --example NAME
fpm run --compiler CMP cargo --profile PROFILE-NAME
DIFFERENCES:
<-- fpm allows multiple names
<-- fpm does not have profiles, just compiler at this time
<-- fpm allows for quoted globbing strings which lets you
easily select all or groups by name substrings
<-- fpm lists available targets if an unknown name or no
name and multiple targets are available, or if special
name "." is specified. From the documentation I do not
see anything indicating if cargo(1) lists targets or
not.
So the common cases are very similiar, with extensions in fpm
to list and run groups of applications using a few special
globbing strings (just going from the cargo documentation; it
might behave differently).
Diffstat (limited to 'test/help_test')
0 files changed, 0 insertions, 0 deletions