retro
| Crates.io | retro |
| lib.rs | retro |
| version | |
| source | src |
| created_at | 2017-05-01 09:42:18.231336 |
| updated_at | 2024-12-09 11:46:24.640194 |
| description | Retro game catalog management. |
| homepage | |
| repository | https://github.com/dirn/retro |
| max_upload_size | |
| id | 12648 |
| Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
Andy Dirnberger (dirn)
documentation
README
retro
Retro game catalog management.
Development
Logging
Logs can be emitted at the following levels: error, warn, info, and
debug. When each level is sent to stdout depends on the log level specified
when invoking retro.
error logs are sent to stdout by default. These should be used anytime the
command takes an action (e.g., a symlink is created). This includes dry runs of
commands. They should also be used to report actual errors.
warn logs should be used when an action is skipped (e.g., a symlink already
exists). They should also be used to report a summary of output that is normally
streamed from an underlying command.
info logs should be used to indicate that no action was attempted (e.g., a
system is not configured).
debug logs should be used sparingly as there may be dependencies that use this
level of logging.