andrew/osupdater
andrew/osupdater
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Added logic for skipping dnf if dnf5 exists. Added roadmap and v1.0 requirements to README.md.

Browse source
This commit is contained in:
Andrew Schott 2024-08-19 20:26:20 -05:00
parent 5c412a7902
commit 9a7c029754
2 changed files with 16 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

16
README.md
View file

@ -7,6 +7,20 @@ This is for my educational purposes of learning rust to do tasks that I have don
Take note that currently, all the used update tools' parameters are hard coded. Down the line, I will incorporate a config file that will have these hardcoded settings as the defaults. Until then, to change said parameters, you _will_ need to edit the source. Take note that currently, all the used update tools' parameters are hard coded. Down the line, I will incorporate a config file that will have these hardcoded settings as the defaults. Until then, to change said parameters, you _will_ need to edit the source.
## v1.0 REQUIREMENTS
Prior to releasing a v1.0, I will need the following features for the CLI version (GUI version will need not exist, but is on the roadmap)
* [DONE] The smarts to not run an old version of a tool if a newer is purposefully installed. This is specifically aimed at dnf/dnf5
* CLI flags to pick and choose what to update and what to skip
* Proper logging -- this means a datestamped file for each tool run plopped into /var/log/
* Stock parameters to be pulled from /etc/osupdater.conf or ~/.config/osupdater/osupdater.conf
## THE ROADMAP : v1.1 AND BEYOND
* Central server for shared configs
* GUI tool that is identical to the CLI version in functionality
* Theming
## **FILES** ## **FILES**
| File | Function | | File | Function |
@ -17,7 +31,7 @@ Take note that currently, all the used update tools' parameters are hard coded.
## **TESTED ENVIRONMENTS** ## **TESTED ENVIRONMENTS**
Currently when I start work on distributions that I do not have a live environment to use or a VM available, I will use distrobox. Then as time permits, I use VMs to test as a next best thing to a live environment. Currently when I start work on distributions that I do not have a live environment to use or a VM available, I will use distrobox. Then, as time permits, I use VMs to test as a next best thing to a live environment.
Consider distrobox tests as the lowest grade pass, then VMs and native tests. Consider distrobox tests as the lowest grade pass, then VMs and native tests.

2
osupdater/src/main.rs
View file

@ -111,7 +111,7 @@ fn main() {
let path_dnf5 = Path::new(&dnf5_bin); let path_dnf5 = Path::new(&dnf5_bin);
if path_dnf5.exists() { if path_dnf5.exists() {
cprintln!("<bold>dnf found but skipped since dnf5 is present</bold>") cprintln!("<bold><rev>dnf found but skipped since dnf5 is present</rev></bold>")
} else if path.exists(){ } else if path.exists(){
cprintln!("<bold><rev>Updating via: dnf</rev></bold>"); cprintln!("<bold><rev>Updating via: dnf</rev></bold>");
let mut cmd = let mut cmd =