Summary: | app-vim/bash-support-4.2.1: file collisions with app-vim/perl-support-5.2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sławomir Nizio <slawomir.nizio> |
Component: | Current packages | Assignee: | Vim Maintainers <vim> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | gentoo3, lssndrbarbieri, toralf |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sławomir Nizio
2014-11-29 20:14:04 UTC
Yep, looks like I overlooked that those language support plugins share some of the same templating code between them. I wish upstream could separate things out cleanly, but I imagine they're just doing bundled plugin installs anyway (probably something vim should aim to support natively at some point). I'll probably hack out the shared files into another plugin that they all dep on at some point if it's possible to do so. *** Bug 536914 has been marked as a duplicate of this bug. *** (In reply to Tim Harder from comment #1) > Yep, looks like I overlooked that those language support plugins share some > of the same templating code between them. I wish upstream could separate > things out cleanly, but I imagine they're just doing bundled plugin installs > anyway (probably something vim should aim to support natively at some point). > > I'll probably hack out the shared files into another plugin that they all > dep on at some point if it's possible to do so. ping just hit this myself. happened today again at tinderbox image 17.0_20170812-170113 Still happens with app-vim/perl-support-5.4 installed and upon attempt to install app-vim/bash-support-4.2.1. * app-vim/perl-support-5.4:0::gentoo * /usr/share/vim/vimfiles/autoload/mmtemplates/core.vim * /usr/share/vim/vimfiles/doc/templatesupport.txt * /usr/share/vim/vimfiles/syntax/template.vim * * Package 'app-vim/bash-support-4.2.1' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. *** Bug 765538 has been marked as a duplicate of this bug. *** |