Description of problem: vim-ale requires vim-enhanced, but it should not because it can work with any Vim package, such as GVim or vimx from vim-X11. I have vim-X11 installed (with alias vim=vimx) Version-Release number of selected component (if applicable): vim-ale-3.1.0-3.fc36 vim-enhanced-2:9.0.077-1.fc36 How reproducible: Always Steps to Reproduce: 1. Make sure vim-enhanced is not installed, but vim-X11 is. 2. dnf install vim-ale Actual results: DNF installs vim-enhanced as a required dependency. Expected results: vim-X11 (GVim and vimx) should be enough. Additional info: It seems vim-X11 provides 'gvim' but not 'vim'; maybe this is a problem with the vim-X11 package instead?
> maybe this is a problem with the vim-X11 package instead? Adding vim maintainer to CC. Zdeňku, what is the expected way to depend on vim-X11 OR vim-enhanced (== vim?)? I think I'll add 'Requires: vim or gvim', but I'd like to know if this is the recommended way to specify dependencies for vim packages.
Hi Pavel, AFAIK there is not one specific recommended way of requiring Vim and I don't prefer one way over the other too much myself, so you can choose from the provides vim-X11 and vim-enhanced have (in case you don't want to depend on package name): 'vim' or '/usr/bin/vim' for vim-enhanced 'gvim' or '/usr/bin/gvim' for vim-X11 Only by guts I would go for the solution you've chosen, but all three are fine. I'm sorry for not answering sooner and I hope it helps.
FEDORA-2022-1af076f59b has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-1af076f59b
FEDORA-2022-1af076f59b has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-67193f4e7f has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-67193f4e7f
FEDORA-2022-16fc4ee6d6 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-16fc4ee6d6
FEDORA-2022-6bb22821b9 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-6bb22821b9
Thank you for the report @Peter, and thanks for the update @zdohnal. I went with this fix eventually: https://src.fedoraproject.org/rpms/vim-ale/c/82ecf296f12009e91e4019eb34bdae022cbf12eb?branch=rawhide I wish we had some guidelines related to vim-* plugin packaging in the future :-)
FEDORA-2022-67193f4e7f has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-67193f4e7f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-67193f4e7f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-16fc4ee6d6 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-16fc4ee6d6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-16fc4ee6d6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-6bb22821b9 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-6bb22821b9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-6bb22821b9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Thank you for figuring this out!
I have used vim-common on various places (vim-nerdtree, vim-command-t). Nobody have complained yet.
Yeah it seems to be the way this is typically done, but it doesn't seem to be correct to me. The `vim-common` doesn't provide a working environment to operate the plugin (Requires: == runtime deps).
(In reply to Pavel Raiskup from comment #14) > Yeah it seems to be the way this is typically done, but it doesn't seem to > be correct to me. The `vim-common` doesn't provide a working environment > to operate the plugin (Requires: == runtime deps). Does it need to? But the true is that vim is probably not part of the base installation anymore, as it used to be. But of course, every vim version could have some virtual provide, such as `vim(runtime_executable)` which the plugins could refer to.
(In reply to Vít Ondruch from comment #15) > But of course, every vim version > could have some virtual provide, such as `vim(runtime_executable)` which the > plugins could refer to. Hi Vita, I've added 'Provides: vim(plugins-supported)' to vim-enhanced and vim-X11 - now I'm going to test it whether it causes some problems. If not, you can use it in packaged Vim plugins.
FEDORA-2022-67193f4e7f has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-6bb22821b9 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-16fc4ee6d6 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.