Upstream Kitty install includes libraries that can potentially break system updates #58
Description
I never made an issue for this at the time, but a year or more ago I was using an upstream build of Kitty which I deployed via my kitty playbook. Later on down the line, in the middle of a zypper dup I started getting a bunch of libreadline errors/warnings as the system installed things using a newer version of libc (I think) than what the libreadline in /usr/local/lib was linked against. But since /usr/local is earlier in PATH, those libs were used instead.
I recall things being FUBAR'd after that and needing to rollback via snapper. I'd like to prevent that in the future should I decide to use an upstream build again. If possible, I should either build from source against my system libraries or exclude some libraries from the upstream tarball.