I don't think you understand what I am saying.

Let me break down into simple steps so that you understand.

Vim is installed on my Slackware system by default.
It was compiled with the following options:
--enable-pythoninterp \
--with-python-config-dir=/usr/lib${LIBDIRSUFFIX}/python$PYVER/config \
--enable-perlinterp \
--disable-tclinterp \
--enable-multibyte \
--enable-cscope \
--with-features=huge

Now, I am guessing that Vim can be compiled with Python and Perl support, and probably needs Python to run. Therefore, I cannot get rid of Python if I want to use Vim. The only way I can know for sure is by reading the README files that come with Vim and seeing what they say.

But, it looks like this whole dependency is optional.

At some stage, somebody decided that this was best for the Slackware install of Vim. They decided this by reading through the README files of Vim and deciding how best to build it, what features to compile in, and what to leave out (such as Ruby support).

What I am saying is: It would be nice to have some indication what went on in this process. Yes, I can open the source and have a look at the README, but there are hundreds of packages installed by default. It would be done while waiting for the package to build. Just a quick note. That is all. I'm not making a formal request. I'm not saying an Application has 1000 README files. Just documentation of what has been done to create this system I am using.

I don't think you understand that what you are saying is not as easy as you think. Just try to do that yourself with a dozen apps, format your results an easy to use way, then come back with your findings.

PS No need to be discourteous with other LQ members, including those who could be more knowledgeable than you.

3 members found this post helpful.

I think you should contact the package maintainer and ask your question. I've done it in the past with some SL packages that were compiled differently than their RH cousins and received a great explanation from the maintainer. Its worth a shot.

That's ignorance on *your* part, not anyone being a "Luddite". What you're saying is people should fix what ain't broke. I've got a word for those kind of people, but I'm a little less rude about mentioning it. Maybe you should follow along those same lines.

FWIW beyond this point I'd like to see more constructive commenting and less rudeness, name calling or whatever else unnecessary and distracting.
Be polite or just don't post, OK?

7 members found this post helpful.

This "somebody" is Pat and he most likely based his decision on the fact, that Slackware provides Python, but didn't provide Ruby at the time VIM was included into the distribution. Ruby made it into Slackware as of release 11.0 while Python was already part of Slackware 8.1 (and maybe earlier releases, but http://packages.slackware.com doesn't cover them).

Also VIM had introduced Ruby support at some point, but may have failed to announce it visibly.
If something is already part of Slackware, it will be used within the distribution. Slackware is not a source-based meta-distribution like Gentoo and it doesn't aim to provide every dependency under the sun like Debian. If VIM would be included today, it would of course get Python and Ruby support, while Lua support would be still left out, because Lua isn't part of Slackware (yet).