| Crates.io | rockfetch |
| lib.rs | rockfetch |
| version | 0.1.7 |
| created_at | 2023-05-28 14:06:37.895661+00 |
| updated_at | 2023-05-28 14:06:37.895661+00 |
| description | An aestethic fetch program written in Rust |
| homepage | |
| repository | https://github.com/DumbMahreeo/rockfetch |
| max_upload_size | |
| id | 876509 |
| size | 27,982 |
A fetch script for completely aestethic purposes.
This is the preferred method, as it allows for configuration.
1.58.0). The preferred way to do so is trough rustup.cargo build --releasetarget/release/. Feel free to strip it with strip target/release/rockfetchThis method is simpler, yet I would suggest the use manual compilation as it allows for configuration, while using cargo install you are forced with the defaults.
With this method simply run the command cargo install rockfetch, and you're all set.
The configurations happens at compile time, simply edit the file: Config.toml. The configuration is always stored in the binary
Since version 0.1.6, to count packages on Fedora, rockfetch will attempt to read the /var/cache/dnf/packages.db database with rusqlite (sqlite3).
Since version 0.1.7, to count packages on Fedora, rockfetch will attempt to read the /var/lib/rpm/rpmdb.sqlite database with rusqlite (sqlite3).
This is default behaviour.
If you'd prefer rockfetch to behave in the old way, calling the rpm command instead of directly reading RPM's package database, disable the fedora-sqlite feature
by compiling with the flag: --no-default-features or by editing the Cargo.toml file manually (removing "fedora-sqlite" from default = [...]).