Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#66353 - [alacritty] install script does not load terminfo file
Attached to Project:
Community Packages
Opened by Jules Sam Randolph (jsamr) - Wednesday, 22 April 2020, 15:13 GMT
Last edited by Jiachen Yang (farseerfc) - Monday, 27 April 2020, 04:51 GMT
Opened by Jules Sam Randolph (jsamr) - Wednesday, 22 April 2020, 15:13 GMT
Last edited by Jiachen Yang (farseerfc) - Monday, 27 April 2020, 04:51 GMT
|
DetailsAs per https://github.com/alacritty/alacritty/blob/master/INSTALL.md#terminfo, the custom alacritty terminfo file must be loaded in terminfo database, otherwise important terminal capabilities would be missing. The instructed way is:
tic -xe alacritty,alacritty-direct extra/alacritty.info The install script does not load such file. |
This task depends upon
Closed by Jiachen Yang (farseerfc)
Monday, 27 April 2020, 04:51 GMT
Reason for closing: Fixed
Additional comments about closing: add ncurses as optdepend in 0.4.2-2
Monday, 27 April 2020, 04:51 GMT
Reason for closing: Fixed
Additional comments about closing: add ncurses as optdepend in 0.4.2-2
In 0.4.1-2 , a new version of ncurses was released that contains alacritty{,+common,-direct} terminfo files, thus conflicted with alacritty-terminfo. So we removed the split pkg:
https://git.archlinux.org/svntogit/community.git/commit/trunk/PKGBUILD?h=packages/alacritty&id=656f7122a01b0d840934a4e3fb06d45b0fe35ee2
Do you have ncurses installed? Maybe we should let alacritty optdepends on ncurses to make this clear.
Yes that was the issue!
I agree, the dependency should be explicit and at least optional.