I've added ebuilds for Vim 6.3b (as -6.3_beta2) to the tree. These are masked by package.mask, since they're beta. It is likely that there will be very few changes between 6.3b and 6.3final, so I'd like to get 6.3b tested on as many archs as possible. The packages in question are: * app-editors/vim * app-editors/vim-core * app-editors/gvim I've removed keywords for archs on which I have not tested. Arch maintainers, please add in ~arch if you feel it's appropriate. I intend to carry over the 6.3b keywords (rather than 6.2) to 6.3final. Method, please check that your selinux patchy magic still works. If you keyword vim-core-6.3b, you should also keyword vim-6.3b and gvim-6.3b (if appropriate for your arch). Things in particular to check for when testing: * Please test both a fresh install *and* an upgrade from vim62. When upgrading, make sure there's nothing left in /usr/share/vim62. We've not had a runtime directory name change for about a year, so this is where things are most likely to explode. * Ensure that the runtime files in /usr/share/vim63b are detected and use. An easy way to check is to edit a .c or .ebuild file and do ':syntax on'. It should show pretty colours and not give lots of scary-looking errors. * Check that the help files work. :help tutor is a good one to try. * Check that any app-vim plugins installed prior to an upgrade still work. Check that app-vim plugins still install afterwards. * Check that :version produces sane output. Sorry if I'm being overly paranoid with this one. It's not so much that I expect it to break, more that I anticipate death threats on the offchance that it does...
I emerged Vim 6.3b on ~x86 after un-hardmasking the ebuild and added the ~x86 keywords to vim, vim-core, and gvim. I then emerged vim-core, vim, and gvim in turn to do an "upgrade". Following this I unmerged gvim,vim,vim-core in order to do a fresh install. I haven't encountered any problems so far but I'll comment on each of the bullet points. I'm not running selinux so I can't comment on the patch magic there. /usr/share/vim62 is gone in both cases and a /usr/share/vim/vim63b replaces it without issue for me. Syntax highlight works fine on an .ebuild or a .c file :help tutor works fine for me I don't use any vim plugins so I can't comment on that. :version VIM - Vi IMproved 6.3b BETA (2004 May 16, compiled May 22 2004 11:12:11) Included patches: 1-2 Compiled by portage@amon Huge version without GUI. <-snip-> Anyway to sum up the change was transparent for me and 6.3b is running fine. However I don't use any plugins.
I unmasked vim vim-core and gvim from package.mask.Although I had to edit the ebuilds of the first 2 to add ~x86, just for gvim I added to /etc/portage/package.keywords "app-editors/gvim ~sparc". Well everything emerged with no further effort. I forgot to check if anything was left in /usr/share/vim62. For both vim & gvim: syntax highlighting works :) ( a c source) :help tutor works :) cream an app that uses vim emerged afterwards and seems to be working as well :) :version produces sane output :) (same as previous post) It seems to be working fine, so I'm going to use it and report back if I find something queer. System and emerge info: [ Colour Code : set unset ] [ Legend : (U) Col 1 - Current USE flags ] [ : (I) Col 2 - Installed With USE flags ] U I [ Found these USE variables in : app-editors/vim-6.3_beta2 ] - - selinux : !!internal use only!! Security Enhanced Linux support, this must be set by the selinux profile or breakage will occur + + ncurses : Adds ncurses support (console display library) + + nls : unknown - - acl : Adds support for Access Control Lists + + cscope : Enables cscope interface -- in vim for example + + gpm : Adds support for sys-libs/gpm (Console-based mouse driver) + + perl : Adds support/bindings for the Perl language. + + python : Adds support/bindings for the Python language - - ruby : Adds support/bindings for the Ruby language + + vim-with-x : Enables linking the console vim against X libs to enable some features in xterms - - minimal : Build vim with minimal features, resulting in a ~430K binary [ Colour Code : set unset ] [ Legend : (U) Col 1 - Current USE flags ] [ : (I) Col 2 - Installed With USE flags ] U I [ Found these USE variables in : app-editors/vim-core-6.3_beta2 ] - - selinux : !!internal use only!! Security Enhanced Linux support, this must be set by the selinux profile or breakage will occur + + ncurses : Adds ncurses support (console display library) + + nls : unknown - - acl : Adds support for Access Control Lists [ Colour Code : set unset ] [ Legend : (U) Col 1 - Current USE flags ] [ : (I) Col 2 - Installed With USE flags ] U I [ Found these USE variables in : app-editors/gvim-6.3_beta2 ] - - selinux : !!internal use only!! Security Enhanced Linux support, this must be set by the selinux profile or breakage will occur + + ncurses : Adds ncurses support (console display library) + + nls : unknown - - acl : Adds support for Access Control Lists + + cscope : Enables cscope interface -- in vim for example + + gpm : Adds support for sys-libs/gpm (Console-based mouse driver) + + perl : Adds support/bindings for the Perl language. + + python : Adds support/bindings for the Python language - - ruby : Adds support/bindings for the Ruby language + + gnome : Adds GNOME support + + gtk : Adds support for x11-libs/gtk+ (The GIMP Toolkit) + + gtk2 : Use gtk+-2.0.0 over gtk+-1.2 in cases where a program supports both. + + motif : Adds motif support (x11-libs/openmotif x11-libs/lesstif) Portage 2.0.50-r6 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3_pre20040420-r0, 2.6.5-gentoo-r1) ================================================================= System uname: 2.6.5-gentoo-r1 i686 AMD Athlon(tm) XP 1800+ Gentoo Base System version 1.4.15 Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=athlon-xp -pipe -fomit-frame-pointer -funroll-loops -ftracer -fmove-all-movables -maccumulate-outgoing-args -fprefetch-loop-arrays " CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=athlon-xp -pipe -fomit-frame-pointer -funroll-loops -ftracer -fmove-all-movables -maccumulate-outgoing-args -fprefetch-loop-arrays " DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X X509 Xaw3d aalib acpi alsa apm atm audiofile avi berkdb bonobo cdr cjk crypt cscope cups dga directfb doc dv dvd dvdr encode esd faad fbcon ffmpeg fommaticdb foomaticdb gdbm geoip ggi gif gimpprint gnome gpm gstreamer gtk gtk2 gtkhtml guile imlib innodb java javamail javascript jbig jikes jpeg junit kerberos krb4 lcms ldap libg++ libwww lua mad matroska md5sum menu mikmod mmx mng motif mozilla mozp3p mozxmlterm mpeg mysql nas ncurses nls nptl objc odbc offensive oggvorbis opengl oss pam pdflib perl png postgres ppds python qt quicktime radeon readline sdl skd skey slang slp speex spell sse ssl svga tcltk tcpd tetex tiff transcode truetype usb v4l v4l2 video_cards_radeon vim-with-x wmf wxwindows x86 xml xml2 xmms xosd xv xvid zlib zvbi"
Keyworded ~alpha.
~amd64
Marked ~ppc yesterday
added ~ia64
Keyworded ~x86
lu_zero marked ~ppc.
Removed x86 CC
[g]vim 6.3b builds fine on x86 :version VIM - Vi IMproved 6.3b BETA (2004 May 16, compiled May 28 2004 16:36:27) Included patches: 1-2 Compiled by root@blackwidow Huge version without GUI. Features included (+) or not (-): +arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent -clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv +cscope +dialog_con +diff +digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +folding -footer +fork() +gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse -mouseshape +mouse_dec -mouse_gpm -mouse_jsbterm +mouse_netterm +mouse_xterm +multi_byte +multi_lang -netbeans_intg -osfiletype +path_extra -perl +postscript +printer +python +quickfix +rightleft -ruby +scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title -toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp -xterm_clipboard -xterm_save system vimrc file: "/etc/vim/vimrc" user vimrc file: "$HOME/.vimrc" user exrc file: "$HOME/.exrc" fall-back for $VIM: "/usr/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -mcpu=athlon-xp -Os -pipe -I/usr/include/python2.3 -pthread Linking: gcc -L/usr/local/lib -o vim -lncurses -lacl -L/usr/lib/python2.3/config -lpython2.3 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic
Builds fine, no crashs or nastiness so far... (build on a ~x86)
Ciaran, I think with this many positive replies on different architectures (and also the fact that the delta between 6.2.x and 6.3b isn't very much) what do you think about just propogating the remaining ~arch keywords forward and closing this bug?
I agree. Since, the versioning scheme that vim has really keeps the changes extremely small, then most likely all the architectures it worked on before will work on the latest 6.3. I move for just ~ARCHing the rest.
Sounds good to me. Looks like the runtime upgrade works perfectly, and nobody spotted the segfault bug anyway (fixed upstream, will be in 6.3final). Remaining keywords added.
removing ppc64 from CC. This bug could be closed I think :-)
