SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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?
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 458
Rep:
Quote:
Originally Posted by FlinchX
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:
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.
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
Last edited by pm_a_cup_of_tea; 06-30-2022 at 08:37 AM.
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.
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.
I didn't try it yet, but are you sure you got an up-to-date SlackBuild?
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:
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.