Packaging languagetool?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- build-system
Research direction
Start by reading utils.py and reviewing staged-recipes for how languagetool and openjdk could be packaged, including the mentioned Java preactivate approach. Done would require an agreed dependency and output structure, a well-known installation location with CLI wrappers, and having this package account for that location.
Written by the indexing model from the issue text.
Description
Hi folks, thanks for maintaining this!
To be able to ship things built on this that work offline (once installed), I'd like to be able to encapsulate the whole dependency tree (languagetool, openjdk) as versioned conda dependencies rather than waiting for import time to download to and update ~/cache.
Since languagetool could be useful outside the context of this package, perhaps that should be added to staged-recipes (potentially built from source), and put in a well-known location (TBD) with CLI wrappers, etc.
This package could then take that location into account. The existing package could become one of a few outputs, e.g. language_tool_python_core, while the new language_tool_python package could depend on *_core and languagetool. This could be done with preactivate scripts (java packages often need these to up CLASSPATH, etc.) but a patch to utils.py might be more sensible.
If (some) of this sounds reasonable, I can take a whack at the languagetool piece!
- Dominant language
- No language data
- Stars
- 1
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the 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.
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
Devolutions/picky-rs#546 · 1 comment ·
Maintainers usually reply within 3 days
-
Add ability to augment cross environment PATH configurationsPossibly taken @bunny953 claimed this today. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
beeware/xbuild#101 · 2 comments ·
Maintainers usually reply within 1 day
-
Needs: Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 3 days
-
area:ci bug triage:confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Cotal-AI/Cotal#2872 · 2 comments ·
Maintainers usually reply within 1 day