More potential paths for busybox executable #40
Merged
Conversation
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
…citly Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Void Linux's busybox-static package, for example, installs it as 'busybox.static'. Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 on a somewhat related note to #13 in aiming to broaden the range of busybox packaging styles virtme can support.
Void Linux offers both statically and dynamically linked versions of busybox in its package repos. Without #13, virtme requires a static build, but unfortunately for virtme Void's busybox-static package installs a binary called
busybox.static(as opposed to thebusybox-staticvirtme currently searches for).So either #13 or this would address the immediate "virtme doesn't work on my distro" problem, though I think there could still potentially be value in both (would support either version of the package instead of requiring the static one).