On Sat, 4 Mar 2017 18:21:23 +0200, gevisz wrote:
> $ eix gvim
> [I] app-editors/gvim
> Available versions: 8.0.0106 ~8.0.0386 **9999 {acl aqua cscope
> debug gnome gtk gtk3 lua luajit motif neXt netbeans nls perl python
> racket ruby selinux session tcl PYTHON_TARGETS="python2_7 python3_4
> python3_5 python3_6"}
> Installed versions: 8.0.0106(05:36:17 PM 12/11/2016)(acl gtk
> python session -aqua -cscope -debug -gnome -gtk3 -lua -luajit -motif
> -neXt -netbeans -nls -perl -racket -ruby -selinux -tcl
> PYTHON_TARGETS="python2_7 python3_4 -python3_5")
> Homepage: http://www.vim.org/ https://github.com/vim/vim
> Description: GUI version of the Vim text editor
>
> So, in my portage tree currently there is one stable gvim package with
> version 8.0.0106
> and one unstable gvim package, with version 8.0.0386.
>
> Why portage force me to unmask an unstable version of the package then?
>
> # emerge --update --deep --with-bdeps=y --newuse --backtrack=90 --ask
> world --exclude chromiumg
>
> These are the packages that would be merged, in order:> [ebuild U ] app-editors/vim-8.0.0386 [8.0.0106] > PYTHON_TARGETS="(-python3_6)" > [ebuild NS ] virtual/libusb-0-r2 [1-r2] ABI_X86="32 (64) (-x32)" > [ebuild U ] app-vim/gentoo-syntax-20170225 [20160530] > [ebuild U ~] app-editors/gvim-8.0.0386 [8.0.0106] Because vim-8.0.0386 is stable and, presumably, the vim and gvim versions must match. I would suggest filing a stabilisation bug for gvim, or just use emacs... -- Neil Bothwick Windows Error #09: Game Over. Exiting Windows.
pgppq7EdxwlPO.pgp
Description: OpenPGP digital signature
