Document dependencies on README
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 50/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- rust
- Domain
- documentation
Research direction
Review README.md and identify the system dependencies needed to build or use the project, starting with the WebKitGTK dependency mentioned in the issue. Check the relevant Repology links and add a concise dependency list with platform or distribution-specific package names where they differ; done means the README makes these requirements clear.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
It would be helpful if the README.md indicated which system dependencies are needed.
e.g. for openSUSE I needed https://repology.org/project/webkit2gtk3-soup2/versions , which is a bit of an odd name. For GUIX it looks like https://repology.org/project/webkitgtk-with-libsoup2/versions is the one. And Redhat & Debian are obviously hiding this under some other package name, which shouldnt be too hard to find.
Describe the solution you'd like
A list of dependencies, with repology links for each if they are spread across multiple names in the repology database, like this one is.
Ideally a bug or PR is raised in repology or elsewhere to have these odd names merged into a single entry.
Describe alternatives you've considered
Another way to assist the user would be to provide these package names in the build error, where it could be customised to the platform/distro being used, but IMO README is probably suffice for now, and is a good step towards any more informative build error message.
Would you assign yourself to implement this feature?
- Yes
- No
Additional context
- Dominant language
- Rust
- Stars
- 100
- Forks
- 19
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tauri-apps/javascriptcore-rs
-
Value::new_function is still in the TODO stage.May be free again @wusyong claimed this 767 days ago, and no pull request is open. Open
tauri-apps/javascriptcore-rs#83 · 1 assignee ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 32/100
tauri-apps/javascriptcore-rs#82 · 1 comment ·
All issues in tauri-apps/javascriptcore-rs
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
install: root SSH tmpfiles.d drop-in is labeled etc_runtime_t instead of etc_tPossibly taken @andrewdunndev claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
[Misdetection] `text/tab-separated-values` file misdetected as `text/tsv`Possibly taken @bact claimed this today. Openmisdetection needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
C-bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
vxc prints a debug line '[flat-codegen] emitted module via the flat path' on every compilePossibly taken @YodHeVauHe claimed this today. Opendevex good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day