TomIO

Make it work technically. Probably. Make it work legally. No. There is no way for us to package a BSL 1.1 project while ensuring we are complying with the license...

I dug up the prior comments on BSL 1.1 by the way. - https://github.com/termux/termux-packages/issues/16229#issuecomment-1521716880 It's not not permissiable, but it needs to be reviewed on a case by case basis,...

Version 1.4.2 is not compatible with modern versions of Zerotier's service, as far as I was aware anyway. So that is gonna have to be a no.

- This was merged in the TUR as termux-user-repository/tur#1112

(Since I'm set as the maintainer for the `bash-completion` package I guess I should chime in.) We could definitely patch the completion until the issue is fixed upstream (be that...

Yep, I can also reproduce this and have already identified the issue. A simple API breakage due to a renamed function in the main `bash-completion` script. https://github.com/scop/bash-completion/blob/master/bash_completion#L760-L786 Should be trivial...

That's bound to happen with AUR packages on Manjaro. AUR package builds are written to work with up to date dependencies from the Arch repos. Manjaro arbitrarily holding back packages...

Mason also does not work particularly well on Termux itself, so it would be nice to have official instuctions for setting up `termux-language-server` with lspconfig.

> If there are issues with using Mason itself then all you need to use lspconfig (as shown above) without Mason is to make sure your nvim config won't call...

- Closed by https://github.com/neovim/nvim-lspconfig/pull/3947