SPECS (AC-branch): vim.spec - updated to 7.1.305 - php.vim updated to 0.9.7...

[Adam Gołębiowski]

On Fri, May 30, 2008 at 09:36:23AM +0300, Elan Ruusamäe wrote:
> On Friday 30 May 2008 01:20, adamg wrote:
> > - vim-heavy / gvim-heavy subpackages (todo done)
> 
> should we perhaps package vim from vim package as vim.ncurses and make symlink 
> to vim and then one can replace the symlink with heavy manually? so it's done 
> line in gvim packages.
> 
> or should we perhaps also overwrite symlink with first vim-heavy install (and 
> restore if uninstalled)?

+1 for packaging vim as vim.ncurses (and perhaps separate vim-ncurses
package).

I was thinking with something like simple vim-config shell script. When
vim/vim-heavy is installed, it checks for /usr/bin/vim existence and
creates such symlink when necessary. When the other package gets
installed, it does nothing, as /usr/bin/vim already exists.

And for those upgrading older vim versions, vim package would create
/usr/bin/vim -> /usr/bin/vim.ncurses symlink.

Sample vim-config usage (idea borrowed from various gentoo's *-config
scripts):

# vim-config --list
  [1] /usr/bin/vim.ncurses *
  [2] /usr/bin/vim.heavy
# ls -l /usr/bin/vim
lrwxrwxrwx 1 root root 8 2008-04-09 21:57 /usr/bin/vim -> vim.ncurses*
# vim-config --select 2
# vim-config --list
  [1] /usr/bin/vim.ncurses
  [2] /usr/bin/vim.heavy *
# ls -l /usr/bin/vim
lrwxrwxrwx 1 root root 8 2008-04-09 21:57 /usr/bin/vim -> vim.heavy*

And similar gvim-config script for gvim. {,g}vim-config would be part of
vim-rt.

Comments?

> should we put suggets: (g)vim-heavy to vim-rt?

-1... maybe suggests: virtual(vim) / virtual(gvim) + appropriate 
provides: in vim-ncurses / vim-heavy

-- 
 http://www.mysza.eu.org/ | Everybody needs someone sure, someone true,
   PLD Linux developer    | Everybody needs some solid rock, I know I do.