rebuild VIM & include vimrc

[mmadia]

 http://dev.haiku-os.org/ticket/5699

 http://dev.haiku-os.org/browser/haiku/trunk/data/etc/vim

To note, Haiku was creating an additional symlink AddSymlinkToHaikuImage? system bin : vim : vi ;

[mmadia]

Seeing as the package needs to be rebuilt for R1 A2, it'd be nice to get this done.

[andreasf]

Replying to mmadia:

To note, Haiku was creating an additional symlink AddSymlinkToHaikuImage system bin : vim : vi ;

Shouldn't that part be taken care of in build/jam/OptionalPackages?

[mmadia]

Replying to andreasf:

Replying to mmadia:

To note, Haiku was creating an additional symlink AddSymlinkToHaikuImage system bin : vim : vi ;

Shouldn't that part be taken care of in build/jam/OptionalPackages?

It could, but the archive already contains some symlinks.
The meat of the ticket is about migrating vimrc from Haiku's repository into the optional package.

[siarzhuk]

Replying to mmadia:

It could, but the archive already contains some symlinks.
The meat of the ticket is about migrating vimrc from Haiku's repository into the optional package.

Optional package already contains all config templates that are required by vim. Why shouldn't just remove this one from the Haiku repository?

PS: I'll take care about a2 rebuild of course. ;-)

[mmadia]

Replying to siarzhuk:

Replying to mmadia:

It could, but the archive already contains some symlinks.
The meat of the ticket is about migrating vimrc from Haiku's repository into the optional package.

Optional package already contains all config templates that are required by vim. Why shouldn't just remove this one from the Haiku repository?

Right. I didn't want to completely remove vimrc from Haiku's jamfiles until it was provided by the optional package archive. ... or do the vim-7.2-x86-gcc2-2009-05-31.zip & vim-7.2-x86-gcc4-2009-05-31.zip already have vimrc in them?

[siarzhuk]

Replying to mmadia:

Right. I didn't want to completely remove vimrc from Haiku's jamfiles until it was provided by the optional package archive. ... or do the vim-7.2-x86-gcc2-2009-05-31.zip & vim-7.2-x86-gcc4-2009-05-31.zip already have vimrc in them?

In my opinion - the vimrc in common/etc/vim is a BeOS legacy. Modern versions of vim use ../share/vim/vimNN/ to look for configuration files. I'm going to check the contents of this file, collect all that can be useful for Haiku and remove it completely in favor of standard configuration files. Do you have any objections?

For what we need that vi -> vim symlink introduced in  http://dev.haiku-os.org/changeset/36082? Is vi still required by some other Haiku utils using it as default editor? In such case we have to fix those tools to using "nano" as default editor instead of adding dangling symlink on optional stuff. Frankly speaking - that was a main reason keeping vim in the Haiku tree - because nobody completely knows from where vi is still referenced. But you have opened this can of worms ;-) - and now it is required to find all refernces to "vi" and replace them with "nano". I think the "vi -> vim" symlink doesn't solve our problem properly.

PS: I found this question significant, and I'm going to copy this my answer in  http://dev.haiku-os.org/ticket/5699 too. Just to take more wide audience in discussion.

[siarzhuk]

Nothing to fix: modern versions of vim doesn't use /etc/ directories for config files. B_USER_SETTINGS_DIRECTORY is used to look for user config files and $VIMRUNTIME for second config files.

Other aspects of mentioned problem can be tracked here:  http://dev.haiku-os.org/ticket/5699.