Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#13240 - [vim] should have language interpeters as optdepends

Attached to Project: Arch Linux
Opened by Greg (dolby) - Thursday, 12 February 2009, 13:16 GMT
Last edited by Tobias Kieslich (tobias) - Sunday, 13 September 2009, 22:50 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


I am opening this to continue no.2 from  FS#13109 

The original poster had said: "Since when does vim require other scripting languages to operate? So far as I know, Ruby and Python arent' required. If they are dependencies for plugins, make that a separate package or something. For those of us with older systems, asking to install another interpreter is like sacreligion! At least make it another package like vim-ruby or vim-python. And if the general user just wants all of vim and it's frills have a meta package called vim-full or something to install the lot."

Allan had agreed (to some extend) : "Making python and ruby optdepends for vim (if they really are only need for plugins) would also fix  FS#11638  "

Edit by Tobias: there is some consideration going on over at  FS#13239  which I think would fix this one as well.
This task depends upon

Closed by  Tobias Kieslich (tobias)
Sunday, 13 September 2009, 22:50 GMT
Reason for closing:  Implemented
Additional comments about closing:  To the best of what is possible. gvim brings you everything you want, vim is sparse but very usable. Ruby will return when (g)vim supports the 1.9 version
Comment by Sleepy_Coder (Sleepy_Coder) - Friday, 13 February 2009, 23:40 GMT
Blah. I sounded so overly-dramatic in the original post... I didn't mean to come across like that. About a week before I made the original post I reinstalled Arch with LUKS and when I went to install vim I thought it was strange that I had to pull in 2 other scripting languages (3 of ruby can be made optional, namcap shows only python and perl are.) and frustrating. It would be nice if they could be separated from the core of vim. :>
Comment by Tobias Kieslich (tobias) - Saturday, 14 February 2009, 00:47 GMT
namcap shows perl and python because they are used on a link level. ruby is loaded via dlopen() and ldd does not see that. but vim starts, fails on dlopen and exits. that pretty much makes it a hard dependency.
Comment by Tobias Kieslich (tobias) - Saturday, 14 February 2009, 01:11 GMT
the good news is I have cooled down a bit, and please note that the rant over at the other bug was not a personal attack. I understand if you saw it that way. But people permanently nag about vi/vim and I actually appreciate that you brought it to the bugtracker, split up into points even if it was later split up more. Don't think your requests are entirely invalid. I'm well aware of the flaws in our layout which is, like anything else with such a complex structure, a compromise.

So if I offended you, this is my apology.
Comment by Aaron Griffin (phrakture) - Sunday, 15 February 2009, 00:19 GMT
Sadly, vim is able to do this just fine on Windows... but it fails on Linux
Comment by Tobias Kieslich (tobias) - Monday, 01 June 2009, 23:31 GMT
Okay, in short ... that's not gonna happen, the buildsystem doesn't allow it. In testing we have a vim depending on perl, gvim on ruby and python (and perl). That's the best I can and will do.
Comment by Tobias Kieslich (tobias) - Thursday, 25 June 2009, 16:22 GMT
vim will use perl as scripting language, gvim perl and python and eventually Ruby again (once vim supports Ruby-1.9 branch)
perl is an optdepend, I think, every other interpreter becomes a hard dependency.