What features/changes would you like to see in future Slackware?

TobiSGD · 06-12-2015, 01:50 PM

Quote:

Originally Posted by mralk3

A newer version of Ruby would be great. The current stable version is 2.2.2. I removed the default ruby-1.9.3_p484 and installed 2.2.2.

Also, Ruby 1.9 is EOL since February.

mralk3 · 06-12-2015, 02:05 PM

Quote:

Originally Posted by TobiSGD

Also, Ruby 1.9 is EOL since February.

Not to mention so many features are unavailable that it's work to make ruby applications backwards compatible. A lot of the newer ruby gems have problems, or cannot be fully utilized.

dugan · 06-12-2015, 02:08 PM

Quote:

Originally Posted by ReaperX7

Is that even possible??? I know a few packages still use Python2 exclusively and haven't added Python3 support yet (I could be wrong though).

I actually think it is. I do know that PyQt, PyKDE, PyGTK all support Python 3. I checked urwid, dbus-python and notify-python and it looks like they support Python 3 too. So I'm pretty confident that Python 3 will support everything that actually needs to be in Slackware.

Mercurial is one notable program that does not support Python 3; it and Python 2 can be moved to /extra.

ReaperX7 · 06-12-2015, 03:00 PM

Doesn't Mesa and LLVM require Python2 still?

dugan · 06-12-2015, 03:42 PM

Quote:

Originally Posted by ReaperX7

Doesn't Mesa and LLVM require Python2 still?

With Mesa I honestly don't know. Haven't checked LLVM.

TobiSGD · 06-12-2015, 04:03 PM

Quote:

Originally Posted by ReaperX7

Doesn't Mesa and LLVM require Python2 still?

Mesa: No. LLVM: Yes.

ReaperX7 · 06-12-2015, 09:28 PM

Well, there goes that idea...

jostber · 06-14-2015, 01:46 PM

GNU Screen 4.3.0:

http://savannah.gnu.org/forum/forum.php?forum_id=8293

ReaperX7 · 06-14-2015, 05:29 PM

I kinda wonder if we move to KDE/Plasma5, if Wayland support (which would pull in libxkbcommon and libinput, and all the XWayland stuff might be worth a try-out?

willysr · 06-14-2015, 07:22 PM

that would be next devel cycle, not this cycle

ReaperX7 · 06-14-2015, 11:14 PM

Sounds good. I have gotten weston built and working on Slackware (and let me pause to say it took a LOT of reworking to do this... ugh! Cairo has to be rebuilt with glesv2 rather than gl, libinput had to be imported, along with libxkbcommon-0.5.0, the proprietary drivers don't work (middle-finger @ nvidia) , rebuilt mesa-10.5.7 with wayland, xorg-server rebuilt with wayland... need I continue? NO!!!) but it does work somewhat, with a few known problems, like Weston refuses to reset the windows and apps each time you close them. I did have to use OpenPAM which luckily worked! Wow... thought that damn thing only used Linux-PAM...

Anyways, due to the fact weston is a P.O.S. I will NOT be uploading it Slackworks... EVER! It's interesting, but at best, it's still crap.

Anyways, maybe I can get KDE rebuilt or Plasma5 imported for wayland...

Drakeo · 06-19-2015, 11:24 AM

I like to see Pat fix the package libxml2 seems the from 14.1 patches to current no longer supply the libxml2.a file which I use to build programs with. I just rebuilt it from source but when your trying to build something global for all to build oh well. One more package I will drop on my bitbucket or github.

Mr. Macintosh · 11-14-2019, 07:58 PM

Quote:

Originally Posted by ReaperX7

Any of the onboard chips usually are still Software Mixing only. I only know of a few onboard devices that actually do(did) hardware mixing and usually those chips are the same ones found on actual sound cards such as the Sound Blaster Emu*-series, C-Media OxygenHD, some older AC97 stuff like the Aureal 8810. Just about everything that is a CODEC style chip HDA or AC97 is software mixing only.

By HDA, do you mean specifically Intel HDA? Would something like Realtek ALC1220 have hardware mixing?