The what should be updated in -current thread

In extra, /brltty deserves an upgrade 4.5 => 5.2: lot of bug fixes, enhancements and new drivers. Just changing the VERSION is enough to build it on Slackware 14.1.

As a side note, I fail to see the purpose of brltty.brlapi.pyx.diff.gz. even though patching that succeeds on the new version as well.

FYI I'm trying to ship brltty in an installer so that blind folks can install Slint/Slackware by themselves.

Originally Posted by heiser891 flac -> 1.3.1 lzip -> 1.16

Got 'em; thanks!

Originally Posted by Speek libogg 1.3.2 libvorbis 1.3.4 wavpack 4.70.0 audacious (+ plugins) 3.5.2 xf86-video-intel 2.99.916 cdrtools 3.01a25

All queued up; thanks!

Originally Posted by andrew.46 Two worthwhile point upgrades would be: slrn upgraded to 1.0.2 irssi upgraded to 0.8.17

Both queued up; thanks!

Has anybody tried the latest rdesktop-1.8.3? I have not bothered, as 1.8.2 is fine for me, but there some enhancements.

Originally Posted by MadMaverick9 dmeventd wants to create its fifos in /var/run. But when /var is a separate partition, dmeventd will not start. May I humbly request that lvm2 be rebuild with the following parameter: --with-default-dm-run-dir=/run/lvm \

Done, along with quite a few other changes to the LVM2 build since 14.1.

And can the following line be added to "/etc/rc.d/rc.S": --- rc.S.old 2014-11-29 10:42:00.912305356 +0700 +++ rc.S.new 2014-11-29 10:43:22.456498581 +0700 @@ -65,6 +65,7 @@ # create some VGs and LVs). if [ -r /etc/lvmtab -o -d /etc/lvm/backup ]; then echo "Initializing LVM (Logical Volume Manager):" + mkdir -p /run/lvm /run/lock/lvm # Check for device-mapper support. if ! grep -wq device-mapper /proc/devices ; then # Try to load a device-mapper kernel module:

I don't understand why this is needed - with all of the rundir stuff set to a subdir of /run, it's created automatically.

I also had to add "/sbin/modprobe -q dm-raid" to be able to setup a raid1 mirror with lvm2.

Hrm, if this is still an issue after the new lvm2 changes go into the tree, let me know and we'll investigate.

Originally Posted by ReaperX7 Here's one good one: procps-3.2.8 > procps-ng-3.3.10 Procps hasn't been developed on in a few years. Procps-ng is now the focus. The newer version will have to probably be packaged separate from psmisc, but here's the build instructions for a SlackBuild targeting procps-ng only... ./configure --prefix=/usr \ --exec-prefix= \ --libdir=/usr/lib \ --docdir=/usr/doc/procps-ng-3.3.10 \ --disable-static \ --disable-kill && make && make install && mv -v /usr/bin/pidof /bin mv -v /usr/lib64/libprocps.so.* /lib64 ln -sfv ../../lib64/$(readlink /usr/lib64/libprocps.so) /usr/lib64/libprocps.so Flag --disable-kill is used to avoid installing the kill utility which is included with util-linux. No patches were required.

Aside from "there's something newer and more maintained" - is there a reason that we need procps-ng instead? I'm not suggesting that it's off the table, but it would be nice to have a real reason for it.

Originally Posted by Didier Spaier gettext and gettext-tools packages can be upgraded to version 0.19.3. No change needed in the SlackBuilds beyond the VERSION. No issue to compile nor run that on a Slackware 14.1, I assume that stands for -current as well. The fixes and enhancements since 0.18.2.1 are worth the upgrade IMO (see relevant part of the NEWS file attached).

Looking into these now.

Originally Posted by allend Has anybody tried the latest rdesktop-1.8.3? I have not bothered, as 1.8.2 is fine for me, but there some enhancements.

Checking on this one now too, as I also use it occasionally...

I'll look into what's been added since the fork of procps to procps-ng, but I do know there were some major updates made to clean up certain parts of the code that resulted in a few patches.

I'd like to see xf86-video-sis updated with this patch to fix a segfault. Upstream isn't really maintaining it anymore.

Originally Posted by elyk I'd like to see xf86-video-sis updated with this patch to fix a segfault. Upstream isn't really maintaining it anymore.

Got it; thanks!

xf86-video-sis and various other drivers are probably not going to be maintained since Mesa3D dropped a lot of the drivers related to DRI1 support. It's really a sad state that support has been reduced to using the vesa/modesetting driver for many non-mainstream video cards over the lack of willingness by the developers to bring the drivers up to modern specs even for EXA.

maybe an upgrade on these:

d/rcs --> 9.3
l/readline --> 6.3
y/bsd-games --> 2.17

Readline 6.3 should have been updated when Bash was originally updated to 4.3. Weird.