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.
It became too long.. The soft is outdated, involving more and more problems on updating it manually.
I spent all the day today just to fuguring out the better way to upgrade my Vim..
Really frustrating
It became too long.. The soft is outdated, involving more and more problems on updating it manually.
I spent all the day today just to fuguring out the better way to upgrade my Vim..
Really frustrating
I don't think Slackware is about novelty or easy of use (whatever that means) - in time I installed it was about to be stable, to run on even very old hardware. I don't think Plasma5 fit that latter description. Slackware evolves in the time - but comparing to the other distributions - rather slow. The are distributions considered to be 'edge' - but it is not about Slackware - Slackware offers good price in terms of novelty/stability - speaking figuratively.
Last edited by igadoter; 03-07-2019 at 11:09 AM.
Reason: spelling, clearing sentence
Grabbing the buildscript from -current and building vim8 for 14.2 worked for me. Though it's the only thing I needed.
Yup, you can very easily update quite a lot of things that way without ill side effects, as long as you know what packages not to mess with. Try doing that on any other distro and watch the package manager go nuts.
It became too long.. The soft is outdated, involving more and more problems on updating it manually.
I spent all the day today just to fuguring out the better way to upgrade my Vim..
Really frustrating
The only program I've run into problems compiling that I really want on 14.2 is kodi v18. It needs a newer version of mesa unless I want to disable VAAPI decoding. There are others that I've run into that are unable to be upgraded, but there weren't any killer features that made me disappointed they couldn't be upgraded.
but it always gives me a bunch of garbage in load:
You got them because you requested them. I use lftp:
Code:
θ70° [ja:/media/data/vim-garbage] $ mkcd /tmp/vim-dl
θ72° [ja:/tmp/vim-dl] $ lftp slackware
cd: received redirection to `https://mirrors.slackware.com/slackware/slackware64-14.2/'
cd ok, cwd=/slackware/slackware64-14.2
lftp mirrors.slackware.com:/slackware/slackware64-14.2> cd ../slackware64-current/source/ap/vim
cd: received redirection to `https://mirrors.slackware.com/slackware/slackware64-current/source/ap/vim/'
cd ok, cwd=/slackware/slackware64-current/source/ap/vim
lftp mirrors.slackware.com:/slackware/slackware64-current/source/ap/vim> mget *
9446084 bytes transferred in 5 seconds (1.74 MiB/s)
Total 18 files transferred
lftp mirrors.slackware.com:/slackware/slackware64-current/source/ap/vim> exit
θ70° [ja:/tmp/vim-dl] $ ll
total 9.1M
-rw-r--r-- 1 ja users 8.1K Jan 19 2006 gvim.png
-rw-r--r-- 1 ja users 118 Aug 24 2006 doinst.sh.gz
-rw-r--r-- 1 ja users 293K Jul 10 2009 ctags-5.8.tar.xz
-rw-r--r-- 1 ja users 834 Feb 27 2018 slack-desc.vim
-rw-r--r-- 1 ja users 959 Mar 15 2018 slack-desc.vim-gvim
-rw-r--r-- 1 ja users 6.1K Nov 14 00:29 vim-gvim.SlackBuild
-rw-r--r-- 1 ja users 283 Jan 11 21:43 vim.vimrc.diff.gz
-rw-r--r-- 1 ja users 7.4K Jan 11 21:44 vim.SlackBuild
-rw-r--r-- 1 ja users 8.6M Feb 27 22:30 vim-8.1.0984.tar.lz
-rw-r--r-- 1 ja users 23K Mar 7 22:35 ctags-5.8.tar.xz.mirrorlist
-rw-r--r-- 1 ja users 22K Mar 7 22:35 doinst.sh.gz.mirrorlist
-rw-r--r-- 1 ja users 22K Mar 7 22:35 gvim.png.mirrorlist
-rw-r--r-- 1 ja users 24K Mar 7 22:35 slack-desc.vim-gvim.mirrorlist
-rw-r--r-- 1 ja users 23K Mar 7 22:35 slack-desc.vim.mirrorlist
-rw-r--r-- 1 ja users 23K Mar 7 22:35 vim-8.1.0984.tar.lz.mirrorlist
-rw-r--r-- 1 ja users 24K Mar 7 22:35 vim-gvim.SlackBuild.mirrorlist
-rw-r--r-- 1 ja users 23K Mar 7 22:35 vim.SlackBuild.mirrorlist
-rw-r--r-- 1 ja users 23K Mar 7 22:35 vim.vimrc.diff.gz.mirrorlist
θ69° [ja:/tmp/vim-dl] $ rm *mirrorlist
θ68° [ja:/tmp/vim-dl] $ ll
total 8.9M
-rw-r--r-- 1 ja users 8.1K Jan 19 2006 gvim.png
-rw-r--r-- 1 ja users 118 Aug 24 2006 doinst.sh.gz
-rw-r--r-- 1 ja users 293K Jul 10 2009 ctags-5.8.tar.xz
-rw-r--r-- 1 ja users 834 Feb 27 2018 slack-desc.vim
-rw-r--r-- 1 ja users 959 Mar 15 2018 slack-desc.vim-gvim
-rw-r--r-- 1 ja users 6.1K Nov 14 00:29 vim-gvim.SlackBuild
-rw-r--r-- 1 ja users 283 Jan 11 21:43 vim.vimrc.diff.gz
-rw-r--r-- 1 ja users 7.4K Jan 11 21:44 vim.SlackBuild
-rw-r--r-- 1 ja users 8.6M Feb 27 22:30 vim-8.1.0984.tar.lz
Yup, you can very easily update quite a lot of things that way without ill side effects, as long as you know what packages not to mess with. Try doing that on any other distro and watch the package manager go nuts.
I got nuts in Slack trying to force work Vim8 from -current in 14.2 (I hate to compile anything without needing)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.