Re: foot: update to 1.12.1.

[ifreund <ifreund@users.noreply.github.com>]

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

New comment by ifreund on void-packages repository

https://github.com/void-linux/void-packages/pull/36884#issuecomment-1122313534

Comment:
Looks like an ncurses update was merged to master in the meantime and we now need to resolve the terminfo conflict one way or another. From foot's `INSTALL.md`:

> As of ncurses 2021-07-31, ncurses includes a version of foot’s terminfo. The recommendation is to use those, and only install the terminfo definitions from this git repo if the system’s ncurses predates 2021-07-31.
>
> But, note that the foot terminfo definitions in ncurses’ lack the non-standard capabilities. This mostly affects tmux; without them, terminal-overrides must be configured to enable truecolor support. For this reason, it is possible to install “our” terminfo definitions as well, either in a non-default location, or under a different name.
>
> Both have their set of issues. When installing to a non-default location, foot will set the environment variable TERMINFO in the child process. However, there are many situations where this simply does not work. See [#695](https://codeberg.org/dnkl/foot/issues/695) for details.
>
> Installing them under a different name generally works well, but will break applications that check if $TERM == foot.
>
> Hence the recommendation to simply use ncurses’ terminfo definitions if available.
>
> If packaging “our” terminfo definitions, I recommend doing that as a separate package, to allow them to be installed on remote systems without having to install foot itself.

It seems like the simplest option is to drop `foot-terminfo`, thoughts?