Right now if vim-syntax is enabled it depends only on vim. Obviously, if I have gvim but not vim installed, I shouldn't have to install vim to use the syntax file. ~ # emerge -p gvim These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] app-editors/gvim-7.0.17 USE="bash-completion gpm gtk perl python ruby -acl (-aqua) -cscope -gnome -motif -mzscheme -netbeans -nextaw -nls" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB ~ # emerge -p conky These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] app-editors/vim-7.0.17 USE="bash-completion gpm perl python ruby -acl -cscope -minimal -mzscheme -nls -vim-pager -vim-with-x" 0 kB [ebuild U ] app-admin/conky-1.4.4 [1.4.3] USE="X audacious hddtemp truetype vim-syntax -bmpx -ipv6 -mpd" 377 kB Total: 2 packages (1 upgrade, 1 new), Size of downloads: 377 kB ~ #
Something else I just noticed: The two other ebuilds in the tree that have vim-syntax in IUSE all depend on the syntax ebuild itself, rather than vim or gvim. For consistency and simplicity it might be easiest to have conky do this as well. (doing it this way would obsolete bug 155119) /usr/portage/sys-auth/openpam/openpam-20050616.ebuild PDEPEND="... vim-syntax? ( app-vim/pam-syntax )" /usr/portage/sys-libs/pam/pam-0.99.6.3-r1 PDEPEND="vim-syntax? ( app-vim/pam-syntax )"
(In reply to comment #1) Eh no? There's no reason to have a separate ebuild for something that's already included in the tarball.
The syntax files were added to the conky tarball as of 1.4.3, since the vim-hosted syntax files are not maintained and are way out-of-date. The ebuild was adjusted to this new setup and there's a bug filed to retire the conky-syntax altogether. If gvim supports the same mechanism as vim, I agree that the conky ebuild could be adjusted to support vim or gvim.
added gvim rdepend so either vim or gvim will satisify dependency. app-vim/conky-syntax is getting removed (bug #155119)- recommend uninstalling it now. Thanks Zack
*** Bug 155479 has been marked as a duplicate of this bug. ***
