Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

"eosio_uninstall.sh --full" to delete directories with configs #5383

Merged
merged 6 commits into from
Sep 5, 2018
Merged

"eosio_uninstall.sh --full" to delete directories with configs #5383

merged 6 commits into from
Sep 5, 2018

Conversation

NorseGaud
Copy link
Contributor

Adding code to support --full for eosio_uninstall.sh to remove directories with configs.

  • I'm sure there are more directories, please add whatever I haven't
  • I would like to add an uninstall guide under "BUILDING EOSIO" on https://developers.eos.io/eosio-nodeos/docs. Can someone add this page for me and I'll suggest the edits?

Thank you

eosio_build.sh Outdated
if [ "$(id -u)" -ne 0 ]; then
printf "\n\tThis requires sudo. Please run with sudo.\n\n"
exit -1
fi
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

eosio_build.sh should not require sudo

@NorseGaud
Copy link
Contributor Author

Curious why you didn't edit and remove the sudo requirement, @heifner?

@heifner
Copy link
Contributor

heifner commented Aug 24, 2018

@NorseGaud it was a bit of a fly-by review. Just not a high priority at the moment. Thanks for the contribution.

@NorseGaud
Copy link
Contributor Author

@heifner Appreciate the follow-up. Just curious if there is a process I should be following to contribute. Want to follow the guidelines if they exist and make your life easier. Thanks

@heifner
Copy link
Contributor

heifner commented Aug 24, 2018

Actually, PRs should be against release/1.2.x if bug fix OR develop if new feature. develop if unsure.

@heifner heifner changed the base branch from master to release/1.2.x August 24, 2018 01:29
@heifner
Copy link
Contributor

heifner commented Aug 24, 2018

As for docs. Pick a close page and suggest edits there.

if [ "$1" == "--full" ]; then
if [ -d ~/Library/Application\ Support/eosio ]; then rm -rf ~/Library/Application\ Support/eosio; fi # Mac OS
if [ -d ~/.local/share/eosio ]; then rm -rf ~/.local/share/eosio; fi # Linux
if [ -d /usr/local/eosio ]; then rm -rf /usr/local/eosio; fi
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Line 33 is redundant, line 24 already deletes /usr/local/eosio outside of the full switch. I like having the other directories guarded off with the full flag, because you might not want to destroy your user/application generated files.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@heifner, @jgiszczak I can't think of any generated (not at install time) files that are placed in /usr/local/eosio, also should we include the keosd generated folders and the opt folders for the boost we install on Linux? This was originally intended to aid in migrating between versions, but with the inclusion of the nodeos directories, it makes me question how clean of an uninstall do we want to go, as in full revert (brew uninstalls that sort of thing).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right, good catch. Thanks!

@NorseGaud
Copy link
Contributor Author

All set I think. Any updates for this?

@heifner heifner merged commit 4c93f42 into EOSIO:release/1.2.x Sep 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants