wcm: support metadata files installed by wayfire-plugin - #124
Merged
Merged
Conversation
Member
|
This is par for the course, so far as wcm is concerned. LGTM, I will assume you've tested this. |
Member
|
Thanks! |
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
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.
Fixes #123
This is the simple way, hardcoding the same path logic that Wayfire uses. As discussed in #123, an alternative would be for Wayfire to export the (relative) paths via pkg-config or similar mechanism. However, I'm now in favor of this simpler option, since:
A further alternative would be for Wayfire to instead always provide the
WAYFIRE_PLUGIN_XML_PATHinstead -- while maybe a bit more complex, in that case, no change to wcm would be needed.