(please respond on -dev, not -core)
This is just a heads-up regarding the vim ebuilds and eclass. Yesterday
I added 6.2a (aka 6.2_pre1) to the tree. It's ~ masked but works fine.
Hopefully I'll be able to unmask it during the next package upgrades
Here are a couple notes:
1. I've removed the setting of VIMRUNTIME from the ebuild. This was
installing /etc/env.d/40vim. There is no reason to set this
variable, since the vim binary has compiled in the location of the
run-time files, /usr/share/vim/vim62a. I have verified this works
for every vim ebuild in the tree, so I don't know what motivated the
"fix" in the first place.
However when you update to the new version, you'll probably notice
that running "vim" (or any of the variants) gives you some warnings,
along with syntax highlighting not working, etc. This is because you
still have VIMRUNTIME in your environment. It won't disappear until
you logout and back in. I'm sorry, but there's no real way to climb
up the process tree and remove VIMRUNTIME from the environment of
each process... :-/
2. Part of my experimentation revealed that vim doesn't yet work with
ruby-1.8.x. I'll be working on this eventually to find and fix the
problem, but for the moment I simply did
DEPEND="ruby? ( =ruby-1.6* )"
You might wonder, why not 1.6.*? Well, Portage didn't like that.
Something to figure out another time.
3. 6.2a says "6.2 alpha". It's hardly alpha. It's really just 6.1 plus
all 474 patches plus gtk2 support. That's why I would consider
marking this stable.
4. This version introduces motif support, so now gvim can produce
an athena, gtk, gtk2, gnome, or motif binary depending on your USE
Have fun and let me know of bugs via bugzilla. I'll be away until
Monday so I won't be responding to email until then.
firstname.lastname@example.org mailing list