split "installation" logic from "bubblewrap" logic#42
Merged
Conversation
Owner
Author
|
@Morganamilo this just moves a few methods from If you want, you can just accept it lightly or skip. |
Owner
Author
|
This is mostly a copy-paste MR, merging. |
vn971
pushed a commit
that referenced
this pull request
Aug 16, 2019
* stop ever relying on current dir, current environment etc. This opens possibility for future concurrent workflow. * add logging * stop enforcing of target/ being the PKGDEST. Use more flexible by-file tar review. * resolve dependencies via RAUR library instead of relying on .SRCINFO-s * add a separate `shellcheck` command for RUA, with built-in handling of PKGBUILD variables * move all `include_bytes!` macros to one place fixes GH-1, fixes GH-41, replaces GH-37, supersedes GH-42.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is a preparation to fix issue #1, similar to the already existing PR #37.