Added Meson build system, appstream metadata and RPM&Yum pieces #161
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
| Build type: native build | ||
|
|
||
| Meson encountered an error: | ||
| First statement must be a call to project |
There was a problem hiding this comment.
Please delete your personal meson-log.txt file from this pull request.
By the way, do you know what this message means? "First statement must be a call to project"
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.
Hi Jaimie,
Ended up working a bit on Remarkable due to using it for converting a document to markdown. The document was instructions for how to get a piece of Software to show up in the desktop software center,
GNOME Software specifically. So I decided to try to make Remarkable the testcase for proofing the documentation. So what I ended up doing was create Meson build files for Remarkable, add a appstream description file, and tweak the Remarkable binary to accept being installed where Meson decides to install it. I finally added a .spec file and a yum repo file pointing to the github hosted repo I set up for testing my Remarkable build and appstream metadata. The resulting RPM works except for the help document, haven't looked into why that doesn't show up.
Apart from that the metadata do allow for Remarkable to show up in GNOME Software as you can see with this screenshot - http://imgur.com/a/rTsyR
Hope some of this work is interesting for you and that you would be willing to host a proper upstream Yum repo for Remarkable(setting it up as the one I am pointing to in the .repo file included) as I would love to make it available through GNOME Software on Fedora.