-
Notifications
You must be signed in to change notification settings - Fork 159
Conversation
Cargo Clippy gives no warnings caused by my changes (checked upstream master and was consistent with that), and I removed the custom Error/Messages handling item, from the requirements. Had help from Leo Spratt (@enchant94) who knows a lot more about rust specific best practices. |
Please remove the swp file that was accidentally added to the commit. |
…n pull request #982
Thanks for letting me know, do let me know if anything needs to be improved, I had no experience with programming in Rust before this, so I made the decision to not add the extra messages as a feature, initially. Do you think it would be worthwhile to add a printout when guix is not found, saying what command to run to install the GNU Guix package manager? If so, Would the method to install GNU Guix stated here, be too long? |
Does anything else need doing for this to be ready for merge? |
* Added new step: guix (basic support) * Fixed clippy errors and better practice, Thanks To guidence from @enchant97 <Leo Spratt> * Removed accidental swp file, as pointed out by @strangelittlemonkey in pull request r-darwish#982 Authored-by: James Clarke <[email protected]> Approved-by: Thomas Schönauer <[email protected]>
Merged at new fork because of inactivity by maintainer. |
Adds support for GNU Guix package manager.
Closes #979
Needs better error handling/messages. But it functions when ive tested it & if the step fails, the program continues as normal.
No custom error messages, happen yet, at the moment error output is just the default from the package manager. see the prior mentioned issue for more details.
I have run the checks, on check that failed, was
cargo clippy
. because of a unneeded return statement, i will fix that warning later. Sorry if my code is not great, i have no experience with rust, until now. Feedback on what to improve would be much appreciated.Standards checklist:
cargo build
)cargo fmt
)cargo clippy
)cargo test
)Features