General question, but many of the packages in both slapt-get and Sourcery are outdated.
I had to build vim from source in order to use the plugin manager I wanted to use.
I am now faced with building node[js] from source for one of my vim plugins to work correctly, and also for web-dev related work. Node in slapt and sourcery is on v.8.x when the current version is 12.x. That's a very old version of an essential (for me) package.
Vim builds fast, but nodejs takes so long I've never actually waited on it completing (like hours).
I do get updates notifications on this installation, but few packages appear to be updated (mostly Firefox and CA-certs).
Is there a reason for slapt-get and Sourcery not getting many package updates?
Am i using an outdated mirror? >> http://ftp.nluug.nl/os/Linux/distr/sali ... ware-14.2/
Are we just waiting for 15.1?
What's up?
Outdated package versions question
Re: Outdated package versions question
Using Sourcery, for example, you can find nodejs-bin, version 14.16.1, with the explanation:chris_alife wrote: ↑14. Nov 2021, 14:15 I am now faced with building node[js] from source for one of my vim plugins to work correctly, and also for web-dev related work. Node in slapt and sourcery is on v.8.x when the current version is 12.x. That's a very old version of an essential (for me) package.
Is there a reason for slapt-get and Sourcery not getting many package updates?
This meta-package uses binary x86_64 distribution as a temporary workaround for the lack of Node.js 10+ in Slackware 14.2.
Perhaps this is suitable for your purposes.
I usechris_alife wrote: ↑14. Nov 2021, 14:15 Am i using an outdated mirror? >> http://ftp.nluug.nl/os/Linux/distr/sali ... ware-14.2/
http://mirrors.xmission.com/salix/x86_6 ... /:OFFICIAL
and
http://mirrors.xmission.com/salix/x86_6 ... /:OFFICIAL
and have this version there as well. Your mirror should be fine on this point.
-
- Posts: 11
- Joined: 13. Dec 2018, 18:45
Re: Outdated package versions question
Hi, thanks for the tip. I couldn't get nodejs to install from sourcery the first couple of times, in fact I couldn't even find it in the beginning, but eventually it installed.
For what I am trying to do, I had to update python past v3.5.1, so I had to build that from source too. But that went fast. Looks like everything is in order and I've had a quick refresher in using configure, make etc
For what I am trying to do, I had to update python past v3.5.1, so I had to build that from source too. But that went fast. Looks like everything is in order and I've had a quick refresher in using configure, make etc
Re: Outdated package versions question
Hello,chris_alife wrote: ↑15. Nov 2021, 18:00 Hi, thanks for the tip. I couldn't get nodejs to install from sourcery the first couple of times, in fact I couldn't even find it in the beginning, but eventually it installed.
For what I am trying to do, I had to update python past v3.5.1, so I had to build that from source too. But that went fast. Looks like everything is in order and I've had a quick refresher in using configure, make etc
Well one does not know offhand on which system characteristics, e.g. kernel and its "accessories" and used compiler and its libraries, the realization of a language and all associated libraries is dependent. That can go already once wrong.
But I am pleased that you have come a step further.