Bug 20171 – vim 6.2_pre2 ebuild doesn't set VIMRUNTIME

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Don Seiler (RETIRED) 2003-04-29 10:11:16 UTC]

Installed vim 6.2_pre2.  After env-update and source /etc/profile, I was still
getting errors due to the VIMRUNTIME env variable not being updated to the new
directory.  Comparing various installs I found that the new install did not set
/etc/env.d/40vim which sets the VIMRUNTIME variable.  This file needs to be
installed and this variable set for vim to work properly.

Reproducible: Always
Steps to Reproduce:

[Comment 1 Don Seiler (RETIRED) 2003-04-29 10:33:04 UTC]

Fudge.  It appears to be something on my system.  I downgraded to vim-core 6.1 r5 and vim 6.1 r21 and the env.d file still wasn't created.  It is there on my home system, just not on my work box now.

Argh.

[Comment 2 Don Seiler (RETIRED) 2003-04-29 11:22:03 UTC]

Ah.  I need to unset the VIMRUNTIME var and then it works.  I don't recall seeing a notice about this, so you might want to post such a notice.

[Comment 3 Aron Griffis (RETIRED) 2003-04-29 16:39:31 UTC]

This is intentional, please see http://article.gmane.org/gmane.linux.gentoo.devel/8120

To solve your problem you should either do "unset VIMRUNTIME" in each terminal, or simply log out of X and back in to unset the variable.  The problem is that you're inheriting VIMRUNTIME from parent processes and there's no way for me to fix that.

[Comment 4 Don Seiler (RETIRED) 2003-04-29 16:49:44 UTC]

Can you not post a notice at the end of the ebuild with this recommendation?  Was it a change in baselayout and NOT vim that occured?

[Comment 5 Aron Griffis (RETIRED) 2003-04-29 16:52:39 UTC]

It was a change in the vim.eclass, and you're right that putting a warning at the end of the build would be a good idea, so I'll do that.

[Comment 6 Aron Griffis (RETIRED) 2003-04-29 17:11:54 UTC]

I've added the warning to the eclass in cvs.  Thanks for the suggestion.