Re: [PR PATCH] [Closed]: [WIP] New package: onivim2-0.5.5

[github-actions[bot] <github-actions[bot]@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]

There's a closed pull request on the void-packages repository

[WIP] New package: onivim2-0.5.5
https://github.com/void-linux/void-packages/pull/31076

Description:
<!-- Mark items with [x] where applicable -->

#### General
- [x] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->

I tried to put together a template based off of the build instructions from upstream and looking at the AUR PKGBUILD. At the moment the build fails at `node install-node-deps.js` in `do_configure`. I noticed there's no `esy` package, so I had it install in `do_configure` with `npm` from `nodejs` package to test build. Not too sure if I did licensing correctly, was no `COPYING` or `NOTICE` or `LICENSE` file or mention of it in `README.md`. So, just did `vlicense` on `ThirdPartyLicenses.txt`. Upstream build and install instructions don't seem to actually tell how to install. Only states that once it's built, can be ran by `esy run`.