Just noticed, the slack-desc of lm_sensors tells me to read README.thinkpad, but no such file have been included since slackware 12.1. Apparently the dangerous versions of lm_sensors were <2.6.4.

1 members found this post helpful.

brltty-4.5 is in /extra. I suggest to ship brltty-5.2 in /ap instead and also to include it in the installer.

I have uploaded here all files necessary to build a full-featured brltty-5.2, including a script /etc/rc.d/rc.brltty to manage the daemon and udev rules to automatically start brltty with a proper driver as soon as a Braille terminal connected via USB is plugged-in. The script bp2cf that comes handy to customize the config file is installed in /usr/sbin. It comes from git because the one in the tarball doesn't work with the new config file format. doinst.sh edits rc.S to start the daemon as soon as the modules are loaded, so that the blind user can "see" all further messages during startup. That's useful if something goes wrong during startup. Of course it would be simpler and cleaner to just update rc.S in the package sysvinit-scripts.

I have successfully built, installed and started brltty-5.2 with this stuff in a clean Slackware64-current today.

In addition the script brltty.installer.SlackBuild makes a stripped down package that is installed in the Slint installer, thus could be installed in the genuine Slackware installer so that a blind user can install Slackware without help from a sighted person. I am ready to adapt instructions in README_BRLTTY to the genuine Slackware upon request.

@Robby: I know that you don't fiddle with this package yourself. Does Patrick read this thread or should I send him an email?

2 members found this post helpful.

Many thank yous for your work here, Didier.

I noticed that libcanberra was only recompiled

News

Tue 25 Sep 2012:
Version 0.30 released; Port to GStreamer 1.0.

as we moved to gstreamer 1.0, I think we should upgrade libcanberra aswell.

How about Subversion 1.8.x? I've been hosting on 1.8.10 for quite a while.

Now that you mention PyQt and since your name appears in the PyQt.SlackBuild, is it possible you could shepherd through a small fix please - regardless of version changes?

One of the products when PyQt.SlackBuild executes 'make' is a file named libpythonplugin.so (in the designer directory). However when 'make install DESTDIR=$PKG' is run, this file is installed directly into the host system rather than into $PKG. The reason is that libpythonplugin.so is built in a directory with python semantics and DESTDIR has no meaning - you can set it to anything you like but it will be ignored. Looking at the install_target in the designer directory's Makefile, you can see that it is looking for a definition of INSTALL_ROOT, not DESTDIR. Since INSTALL_ROOT is meaningless everywhere else, the simple fix which would restore libpythonplugin.so to the final package is to change the line to The libpythonplugin.so file is what enables Qt Designer files to be recognized/used in a PyQt application. For those of us using Designer, it would be great to have this facility back without having to rebuild the package ourselves.

chris

1 members found this post helpful.

I really do enjoy and use the e-mail clients that ship with Slackware. I would like to see claws-mail and libetpan added to -current. Claws-mail is a very fast, feature-rich e-mail client.

P.S. I realize this is more of an addition than an update.

There may be another reason to add ConsoleKit2 and LoginKit (I'll get a prelim Slackbuild drafted for this). ConsoleKit still lacks the inhibit() function though ConsoleKit2 added multiseat function. The good thing is CK2 fully supports the xfce-power-management logind functions. This may work with the newer upower, though I'd have to do a build check. I'll try building it tomorrow or next week when I have time. This would help with fully supporting DEs that may use logind rather than ConsoleKit.

I'd have to give this some work, but hopefully these can be useful.

Robby, I may submit ConsoleKit2 and LoginKit to SBo, when the buildscript for LoginKit is tested and completed.

Hi Chris

I will use that when I work on updates for my KDE Plasma 5 packages. I will slip in a new sip and PyQT - perhaps new packages supporting Qt5 as well.

As for the official Slackware package: my name is in it, but after it got added to Slackware, control was transfered to Patrick.

If at some point gcc-4.9.2 is going to be recompiled, say for example, to add the missing libiberty.a, it would be the ideal time to first upgrade libmpc.

2 members found this post helpful.

Great thread. Some of the things from my wish list has already been mentioned (e.g. subversion 1.8.x) but one thing that I can add is swig:
The latest updates have swig-2.0.12 and I think it would be a good idea to move to version 3 instead of 2. Version 3.0.5 is the latest one.

Feature highlights from 3.0 is nested class support and many c++ improvements including c++11 support.

Depending on which other slack packages that depend on swig, this update could cause some issues since the 3.0 release do have
some potential incompabilities according to the release notes.

Since I haven't posted before, I can't write out the full links:
swig.org/Release/RELEASENOTES
swig.org/Release/CHANGES

libvpx 1.3.0 was added on Tue Apr 21, but
libvpx 1.4.0 is released already.
https://groups.google.com/a/webmproj...el/2zYWenmdUM8

We made the intentional decision to wait with this one, since it's breaking some things. But it's definitely on the TODO list.

2 members found this post helpful.

Kind of a big request, but I would love to see make 4.1 hit the tree. :-)

If that happens, don't blame the tree

2 members found this post helpful.