Seperate plugins from vib codebase #52
Merged
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
axtloss
force-pushed
the
feat/seperate-plugins
branch
5 times, most recently
from
c23ebf9
to
a68fd99
Compare
matbme
reviewed
May 21, 2024
axtloss
force-pushed
the
feat/seperate-plugins
branch
from
a68fd99
to
411889f
Compare
matbme
approved these changes
May 21, 2024
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.
This separates our builtin plugins (except for
shell) from the vib codebase, making vib more versatile and lighter as it does not force the plugins we use in vanilla os.As part of the separation it is possible to install system wide vib plugins into
/usr/share/vib/pluginswhich can be used in any project but will not be preferred over local plugins.This is part of an ongoing effort to rework the vib api to work with more programming languages.