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.
I would disagree on that one. Slackware is a very good distribution for developers as it has a lot of nice libraries and don't separate those libraries in "standard packages" and "developer packages". I am also very happy with the fact that valgrind will be included out of the box in the next upcoming Slackware release. Valgrind is an example of a tool mostly used by developers.
regards Henrik
At one point I was the sole Linux programmer in a Microsoft shop. I think some of the code I developed is still in use a decade and a half later. I used Slackware for that. I played with some IDEs, but I wound up using vim and Make for the heavy lifting.
But I would think simpler things, like sway, hyprland, labwc, etc fit the mold much better. There are a ton of required packages for the entire nwg-shell environment (including the aformentioned ones). But LxQT would be a perfect addition I believe (and 2.0 does work just fine!). The panel bug which was found, has been patched.
Sorry, surely not an attack I didnt knew you had that stuff over there. Thanks for pointing this out.
Patrick, I just checked and libncurses++.so.6 still resided in my Slackware distro, and it is pointing to libncurses++w.so.6 with is not ABI compatible.
Patrick, I just checked and libncurses++.so.6 still resided in my Slackware distro, and it is pointing to libncurses++w.so.6 with is not ABI compatible.
From the changelog:
Code:
Mon Apr 29 21:32:37 UTC 2024
...
l/ncurses-6.5-x86_64-1.txz: Upgraded.
This seemed like a good opportunity to go over my notes and try to make this
SlackBuild at least defensible, if not correct. :-) The non-wide libraries
have all been purged and replaced with compatibility symlinks pointing to the
wide versions. Anything trying to use -lncurses (etc) will be redirected to
-lncursesw (etc) at compile time. Looks like nearly 50 packages are linked to
the non-wide libraries, but everything works this way.
Thanks to GazL who provided most of the suggestions used.
Mon Apr 29 21:32:37 UTC 2024
...
l/ncurses-6.5-x86_64-1.txz: Upgraded.
This seemed like a good opportunity to go over my notes and try to make this
SlackBuild at least defensible, if not correct. :-) The non-wide libraries
have all been purged and replaced with compatibility symlinks pointing to the
wide versions. Anything trying to use -lncurses (etc) will be redirected to
-lncursesw (etc) at compile time. Looks like nearly 50 packages are linked to
the non-wide libraries, but everything works this way.
Thanks to GazL who provided most of the suggestions used.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
I didnt knew you had that stuff over there. Thanks for pointing this out.
