Dne 02. 04. 21 v 13:37 Christian Boltz napsal(a):
You could argue this way for basically everything - whatever the distribution ships puts a MitM between the user and upstream, sometimes delays the update because the packager is busy with other stuff, and maybe makes local updates more complicated.
No, I cannot, and you don't seem to read what I wrote. For complex packages (Python- or whateverelse- based) we provide unbundling, automatic updates (including updates of unbundled libraries), fixing integration issues, a lot of things. What value we bring for a vim plugin? * no unbundling (in 99% case there is nothing to unbundle) * no integration issues (I don't know how or even if we deal with vim/neovim distinction, and that's the only possible issue which comes to my mind) * slower updates (whichever method of vim package management you use, it is faster than waiting on openSUSE packages) * slower access to the issue resolution
Yes, this sometimes means shipping older software than available upstream, but I happily pay that price if it saves me from having to manage my vim plugins, python modules, ... myself.
From 79 vim plugins I have installed, you have only four and even those are completely obsolete. Older software? vim-plugin-fugitive in Factory is from 2019-10-11! I have latest update of fugitive (with fixes I've negotiated with upstream recently) from 34 hours ago.
Also, whenever someone asks "does packaging $whatever make sense?", just answer "yes" unless you have a very good reason for a different answer.
I agree, but for vim plugins there are plenty of very good reasons for a different answer. See above. Best, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mcepl@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 I love deadlines. I like the whooshing sound they make as they fly by. -- Douglas Adams, The Salmon of Doubt