This is adding another LSP to the ports for lang/janet.
Details
- Reviewers
adamw hsw_bitmark.com - Commits
- R11:cfcfb64aa315: devel/janet-lsp: Add port
Build and run in stable/14, stable/15, and current. The source for janet-lsp itself is a good project to try and verify with.
make test also passes.
Diff Detail
- Repository
- R11 FreeBSD ports repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
{F139748281}
poudriere-testport(8) output, were it not for this I would have missed the git rev-parse in the janet-lsp code!
| devel/janet-lsp/Makefile | ||
|---|---|---|
| 16 | Does it need a RUN_DEPENDS on janet in your opinion? | |
| 44 | Generally we would not indent the .for like that in a do-* target. | |
| 45 | jpm should be called with its absolute path, based on ${LOCALBASE}. | |
| devel/janet-lsp/pkg-descr | ||
| 2 | You probably want a full sentence here, not a clause. Only COMMENT has weird grammatic restrictions. | |
| devel/janet-lsp/Makefile | ||
|---|---|---|
| 16 | One of the very cool things about Janet is its deployment story. It can build to a "binscript" like jpm(1) which is similar to how Python would install. Or, like here, it can build to a static executable similar to golang. I chose a static executable, but not just for convenience. This uses a non-released version of the "cmd" library. If I made it a binscript and some other janet port comes along that wants an official "cmd" they would conflict. So in this configuration it does not need RUN_DEPENDS. | |
Address review comments:
- place .for at line beginning.
- use LOCALBASE to invoke jpm.
- update pkg-descr
rechecked portlint -A, portfmt --strict, and rebuilt with poudriere testport.
| devel/janet-lsp/pkg-descr | ||
|---|---|---|
| 2 | Its still terse, but this is all it does. It may not have all the LSP features but it is still usefull. | |
Great work on this! I made two [edit: counting is hard] small changes:
- Added a space after && in do-build:.
- Removed the comment about appeasing portlint. I personally loved it and thought it was a great way to pet the portlint, but it doesn't belong in production. I'd much rather that we all ignore unnecessary warnings, rather than alter ports in weird ways to silence it.
- Broke a long line in do-install:.
I'm thrilled to see more LSPs! I've been intending to make a port for npm @tailwindcss/language-server for a while now. There are lots of great LSPs out there, especially those in nvim-lspconfig, and we have packages for only a handful of them.