LinuxQuestions.org - Vim9 in Slackware-15.0

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Vim9 in Slackware-15.0 (https://www.linuxquestions.org/questions/slackware-14/vim9-in-slackware-15-0-a-4175714008/)

Vim9 in Slackware-15.0

Now that Vim9 is out, but stable versions of Slackware generally only get security patches, what's the future of Vim9 in Slackware-15.0, how will it happen?

Will Pat make an exception and bump it to Vim9 in 15.0 if it behaves well for a while in -current?

Will Vim9 rather be provided as extra/ package a la llvm in 14.2?

Will it be rather possible to install Vim9 alongside Vim8?

Will it appear on SBo and make its way into next stable Slackware version through -current?

Quote:

Originally Posted by FlinchX (Post 6364318)

Will it be rather possible to install Vim9 alongside Vim8?

There would be some file conflicts to work out (binaries and man pages), but at least everything in /usr/share/vim would be separated. /usr/bin/ctags appears to retain the same version from Vim8. I'm not sure what would be appropriate for /usr/bin/xxd, though.

You can just grab the source directory from -current and build it on 15.0 yourself. I did this for a few years during the 14.2->15.0 transition. I haven't yet restarted the practice because 15.0 isn't that old. Maybe I'll reconsider since Vim9 is now released. But actually the version of Vim in Slackware 15.0 (8.2.4649) isn't all that different from Vim 9.0:

https://www.vim.org/vim90.php

Quote:

Vim 9.0 released
After many years of gradual improvement Vim now takes a big step with a major release. Besides many small additions the spotlight is on a new incarnation of the Vim script language: Vim9 script.

The previous release was version 8.2 in December 2019. Since the latest source code is always available on GitHub, many have already picked up later patch versions (there are more than 5000 of them!). Therefore the changes have already been tried out by many users. On top of that bugs have been fixed, security issues have been addressed, and many tests have been added. Code coverage has been dramatically increased. This version is more reliable than any before.

Quote:

Originally Posted by drumz (Post 6364379)

You can just grab the source directory from -current and build it on 15.0 yourself.

https://www.vim.org/vim90.php

I did this with emacs28. Downloaded the slackbuild and source, build it as you would an SBo package then use upgradepkg to install. Its really as simple as that :)

Vim 9.0 is now available in Slackware-current.

I've built both vim and gvim packages on Slackware-15.0 using sources from https://mirrors.slackware.com/slackw...source/ap/vim/.

However for the moment it is necessary to correct *.SlackBuild scripts - the Vim version (VIMBRANCH) inside is incorrect - 8.2 (should be 9.0) and scripts try to get source from github instead of using available *.tar.lz archive.

Quote:

Originally Posted by at0 (Post 6364813)

I didn't try it yet, but are you sure you got an up-to-date SlackBuild?

https://git.slackware.nl/current/tre...SlackBuild#n26

Code:

VIMBRANCH=9.0

https://git.slackware.nl/current/tre...SlackBuild#n33

Code:

if [ -r vim-${VIMBRANCH}*.tar.?z ]; then # if there's a source archive already, use the version number from it:

  VERSION=$(echo vim-${VIMBRANCH}*.tar.?z | rev | cut -f 3- -d . | cut -f 1 -d - | rev)

else # need to fetch the latest source archive for this branch:

Edit:
And here is the only change made to vim.SlackBuild:
https://git.slackware.nl/current/dif...ed604115aede58

Code:

diff --git a/source/ap/vim/vim.SlackBuild b/source/ap/vim/vim.SlackBuild

index 64ad16bb..503f5cf6 100755

--- a/source/ap/vim/vim.SlackBuild

+++ b/source/ap/vim/vim.SlackBuild

@@ -23,7 +23,7 @@

 cd $(dirname $0) ; CWD=$(pwd)

 

 PKGNAM=vim

-VIMBRANCH=8.2

+VIMBRANCH=9.0

 CTAGSVER=5.8

 BUILD=${BUILD:-1}

Quote:

Originally Posted by drumz (Post 6364873)

I didn't try it yet, but are you sure you got an up-to-date SlackBuild?

https://git.slackware.nl/current/tre...SlackBuild#n26

Code:

VIMBRANCH=9.0

Thanks. At the moment of writing that was the case. I've used lftp -c 'open -e mirror ...' to get that folder from http://mirrors.slackware.com.
Neither direct download of *.SlackBuild's resolved that problem.

However it's quite possible that the mirror I've got sources from was not yet fully updated.

For the moment I also get *.SlackBuilds with correct VIMBRANCH=9.0.

Good to know that was just my "problem" though.