build.sh now working differently #48
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 4 commits
May 10, 2017 17:06
…on containing config.conf and conflicts.txt
|
Sorry for the "macOS fix" it's from 1Conan. Hopefully he's ok with it. (I'm using it here) |
|
This didn't totally follow the styleguide. |
|
Feel free to improve it. (Also styling) What do you mean by "not very portable"? Do you mean it only runs in bash? We could use awk I guess, but I don't know how to use it correctly. I think this is a bit more user friendly, since you only have to create a new folder + a configuration file + conflictsfile |
added 2 commits
May 11, 2017 07:15
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Just create a new folder, add a config file and a conflicts file and run ./build.sh foldername and you´ll get a new gandalf version. Maybe incompatible with #47. @1Conan.