We have a lot of packages in app-vim, and all of them should support both neovim and vim (because neovim is compatible with most things from vim-7.4), but we can only build and use them with vim. The easiest way I can imagine doing this is introducing a new global USE flag, "nvim" or "neovim", and changing the vim-plugin, vim-spell, and vim-doc eclasses to reflect the different runtime path: "/usr/share/nvim/runtime" instead of "/usr/share/vim/vimfiles". Another possible way we could do this is by adding a new USE_EXPAND, named something like "VIM_TARGETS" with possible values of "vim, neovim" and we install to each of the possible targets so that users can choose to support both vim instances.
I just attempted to created one solution to this problem (though it's not cleaned up because I'm not sure whether it would get accepted) available at https://github.com/lluixhi/gentoo/tree/neovim-syntax Adding a `vim-runtime.eclass` and inheriting from that in order to set the vimfiles directory.
Aric, I see that your eclass proposal had been reviewed, do you plan to continue working on it?
If there is some work I could do, let me know. It was too bad to not use all app-vim/* packages for neovim, too.
Is this bug dead? I would be great to be able to have only neovim installed, and not an unused vim/vim-core installation.
Worst case, I or someone else could set up ebuilds for this on an overlay.
There's an opportunity to implement such support -- Vim eclasses are being ported to EAPI 8. https://github.com/gentoo/gentoo/pull/24941
