LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Requests for -current (14.2-->15.0) (https://www.linuxquestions.org/questions/slackware-14/requests-for-current-14-2-15-0-a-4175620463/)

rworkman 12-28-2017 03:49 PM

Requests for -current (14.2-->15.0)
 
The previous thread has gotten quite long, so it's a good time to start a new one.

Current state of things is this:
* rc.6 change for fuser is queued
* greylist.pl addition to postfix is queued
* lvm2, tin, ModemManager, whois, xine-ui, bluez, v4l_utils, mpfr, doxygen, ca_certificates, tar as mentioned in previous thread - all queued
* udisks-2.7.x and its deps are queued, but no promises on those
* xapian_core, enchant, and grantlee all have queued updates, but those might wait for (assuming it happens) new KDE/Plasma
* newer upower and ConsoleKit2 have to wait for new KDE/Plasma
* kernel 4.14.x is still desired but still not ready, it seems
* everyone already knows about PAM

TODO items:
* Jakub Jankowski has a seems-to-be-working patch for vlan support in network-scripts; see the "vlan" branch here: https://git.rlworkman.net/slacknetsetup/
* if anyone has some free time and wants a challenge, figure out a way to do ipv6 support such that it integrates nicely and works well; good luck. :-)

Skaendo 12-28-2017 05:36 PM

My only thought would be KDE5. But since that is not going to happen, Slackware 14.3.

rworkman 12-28-2017 05:57 PM

Quote:

Originally Posted by Skaendo (Post 5799026)
My only thought would be KDE5. But since that is not going to happen, Slackware 14.3.

What part of this makes you so sure it's not going to happen?
Code:

* xapian_core, enchant, and grantlee all have queued updates,
  but those might wait for (assuming it happens) new KDE/Plasma
* newer upower and ConsoleKit2 have to wait for new KDE/Plasma


Darth Vader 12-28-2017 06:06 PM

Quote:

Originally Posted by Skaendo (Post 5799026)
My only thought would be KDE5. But since that is not going to happen, Slackware 14.3.

I think I got it what make our BDFL reluctant about Plasma 5; it is plain and simple: its infernal release period, a monthly one.

Combine that with its really huge number of packages, and you get The Perfect Storm. ;)

Did you really believe that Patrick Volkerding would be so happy to update every month roughly a third part of the distribution packages? :D

Myself I would not be.

---------------------------------------
To be on topic: how about the addition of SMPLAYER, a small but powerful frontend for MPlayer and, optionally, MPV?

To note that its build depends only on Qt (either the version 4 or 5).

https://www.smplayer.info/

dugan 12-28-2017 06:10 PM

This is at least the third time I've asked for this:

FluidSynth, and both sdl and SDL2_mixer rebuilt to use it.

That gets the SDL libraries to support MIDI playback. You just set the SDL_SOUNDFONTS environment variable to be the path to a soundfont in .sf2 format, set up your game to use MIDI for playback, and enjoy.

DosBox and (AFAIK) all DOOM source ports support playing MIDI via SDL, which this is needed to enable.

I wrote a blog entry about this back in (* checks date) 2011, which shows how long it's actually been available:

http://duganchen.ca/playing-sdl_mixe...th-soundfonts/

bassmadrigal 12-28-2017 06:17 PM

I had mentioned this on the old thread (twice), but it doesn't seem to be addressed. It may just be that it is deemed as a non-issue, which I am fine with. But I just wanted to make sure it wasn't accidentally skipped over. The first post is below with an updated patch to match the latest binutils.SlackBuild script.

======================================

Based on this topic, it seems that on 64bit systems, /etc/ld.so.conf points to the wrong directory for the /usr/x86_64-slackware-linux/lib64 entry, because there is no lib64 directory under /usr/x86_64-slackware-linux/, only lib.

There are two potential fixes I see for this, one being to modify etc.SlackBuild to somehow adjust the sed line that changes all the lib dirs to lib64 to somehow exclude this one, or to adjust binutils.SlackBuild to change that directory to lib64 on 64bit machines. I think the latter is quite a bit easier, so I threw together a quick patch for the SlackBuild.

Code:

diff --git a/binutils.SlackBuild b/binutils.SlackBuild
index c3b475e..87c521a 100644
--- a/binutils.SlackBuild
+++ b/binutils.SlackBuild
@@ -162,7 +162,7 @@ make install DESTDIR=$PKG || exit 1
 # Move ldscripts to /usr/lib${LIBDIRSUFFIX}, and then put symlinks in place
 mv $PKG/usr/${TARGET}/lib/ldscripts $PKG/usr/lib${LIBDIRSUFFIX}
 ( cd $PKG/usr/${TARGET}
-  ln -s /usr/lib${LIBDIRSUFFIX}/ldscripts lib/ldscripts
+  ln -s /usr/lib${LIBDIRSUFFIX}/ldscripts lib${LIBDIRSUFFIX}/ldscripts
  for FILE in ar as ld ld.bfd ld.gold nm objcopy objdump ranlib strip ; do
    if [ -r "/usr/bin/$FILE" ]; then
      rm -f bin/$FILE

It likely isn't a big deal as there doesn't seem to be anything residing in there other than a symlink for ldscripts that points to /usr/lib${LIBDIRSUFFIX}/ldscripts/, but it probably wouldn't hurt to make sure ld.so.conf points to the correct directory anyway :)

Daedra 12-29-2017 12:51 AM

Quote:

Originally Posted by Darth Vader (Post 5799041)
I think I got it what make our BDFL reluctant about Plasma 5; it is plain and simple: its infernal release period, a monthly one.

Combine that with its really huge number of packages, and you get The Perfect Storm. ;)

Did you really believe that Patrick Volkerding would be so happy to update every month roughly a third part of the distribution packages? :D

Myself I would not be.

---------------------------------------
To be on topic: how about the addition of SMPLAYER, a small but powerful frontend for MPlayer and, optionally, MPV?

To note that its build depends only on Qt (either the version 4 or 5).

https://www.smplayer.info/

Looks like there will be a KDE 5 LTS version coming next month https://www.phoronix.com/scan.php?pa...5.12-LTS-Plans

RadicalDreamer 12-29-2017 12:55 AM

I think Qt4 should be removed and at least Qt5 be added. Its not that Qt4 is bad. Its really nice but it has been abandoned and everything is pretty much Qt5 now. I'd like to see FFmpeg and SDL (as dugan mentioned) tricked out more. FFmpeg isn't a big deal for me because of the excellent SlackBuild it has. I use the Slackware FFmpeg package on a laptop and trick out ffmpeg more for my desktop. I would really like OpenAL to be added, and opencv would be nice.

What do you all do with mpv anyway? I don't get why mplayer doesn't suffice? I use QMPlay2 because I can add folders with videos, sync them easy, access the playlist easily, and watch youtube with it. Also CUVID+NVIDIA = godlike. It has way better performance than VLC and it always performs flawlessly. Its easy and quick to build. Based on popularity VLC would make the most sense to add.

gmgf 12-29-2017 01:48 AM

Quote:

Originally Posted by Daedra (Post 5799131)
Looks like there will be a KDE 5 LTS version coming next month https://www.phoronix.com/scan.php?pa...5.12-LTS-Plans

I think it's better here :)

https://community.kde.org/Schedules

1337_powerslacker 12-29-2017 01:51 AM

Quote:

Originally Posted by RadicalDreamer (Post 5799132)
What do you all do with mpv anyway? I don't get why mplayer doesn't suffice?

The interface is simpler to control ( I just use the left & right arrow keys to control the video, and use similar keyboard shortcuts to achieve desired effects). MPlayer just doesn't have the same feel.

Just my :twocents:

gmgf 12-29-2017 03:57 AM

Another new imagemagick-6.9.9-30:

https://www.imagemagick.org/download....9.9-30.tar.xz

Robby, just for info, latest udisks-2.75, 'and lib*, work here, without problem:

https://github.com/storaged-project

burdi01 12-29-2017 04:26 AM

Making slackpkg $ROOT aware
 
As per https://www.linuxquestions.org/quest...re-4175600630/ ...
:D

Skaendo 12-29-2017 05:47 AM

Quote:

Originally Posted by rworkman (Post 5799035)
What part of this makes you so sure it's not going to happen?
Code:

* xapian_core, enchant, and grantlee all have queued updates,
  but those might wait for (assuming it happens) new KDE/Plasma
* newer upower and ConsoleKit2 have to wait for new KDE/Plasma


I don't know, unless PV wants to release 15 with limited testing with Plasma or listen to a bunch of people crying about 'when is Slackware 15 coming out', it only makes sense to me to release 14.3 and push Plasma to current. It doesn't really matter to me either way, I don't use KDE.

gmgf 12-29-2017 06:18 AM

I'm not sure that release a new version with a lot of software, not maintained, is a good idea, but it's just my opinion ;)

ponce 12-29-2017 06:29 AM

as we have often experienced people will whine in either case so the whining shouldn't really matter when deciding, IMHO ;)

Alien Bob 12-29-2017 06:34 AM

Quote:

Originally Posted by Skaendo (Post 5799202)
I don't know, unless PV wants to release 15 with limited testing with Plasma

And what makes you think that Pat is going to add Plasma 5 and then immediately release Slackware 15.0? Ever heard of public betas? We have not seen any yet.
About the "limited testing" of Plasma 5 - I have been providing monthly updates to a Slackware Plasma 5 desktop for more than THREE years now, starting when the latest stable Slackware release was still 14.1. There has been a lot of feedback on those packages used by many, so I would not call it "limited testing".

GazL 12-29-2017 07:10 AM

As someone who replaces rc.inet1 with their own version it would be convenient for me to see rc.inet1 given the '.local' treatment just like rc.4 recently got, but I don't know whether it would be of benefit to anyone else so I'll stop short of asking for it outright and just throw the idea out there for contemplation. :)

Alien Bob 12-29-2017 07:30 AM

Quote:

Originally Posted by GazL (Post 5799229)
As someone who replaces rc.inet1 with their own version it would be convenient for me to see rc.inet1 given the '.local' treatment just like rc.4 recently got, but I don't know whether it would be of benefit to anyone else so I'll stop short of asking for it outright and just throw the idea out there for contemplation. :)

Well it's as simple as:
Code:

eha@bigfoot:/stuff/slackware/non-public/alien/slackware64$ diff -u source/a/sysvinit-scripts/scripts/rc.M{.alien,}
--- source/a/sysvinit-scripts/scripts/rc.M.orig        2017-11-18 18:21:12.000000000 +0100
+++ source/a/sysvinit-scripts/scripts/rc.M      2017-12-29 14:28:02.408497854 +0100
@@ -95,7 +95,9 @@
 fi
 
 # Initialize the networking hardware.
-if [ -x /etc/rc.d/rc.inet1 ]; then
+if [ -x /etc/rc.d/rc.inet1.local ]; then
+  /etc/rc.d/rc.inet1.local
+elif [ -x /etc/rc.d/rc.inet1 ]; then
  /etc/rc.d/rc.inet1
 fi

... so I hope Patrick picks this up. I think it is a good addition.

gmgf 12-29-2017 12:48 PM

libzip-1.4.0:

(Improve build with cmake
Retire autoconf/automake build system)
https://libzip.org/news/
https://libzip.org/download/libzip-1.4.0.tar.xz

rworkman 12-29-2017 03:09 PM

Quote:

Originally Posted by gmgf (Post 5799359)
libzip-1.4.0:

(Improve build with cmake
Retire autoconf/automake build system)
https://libzip.org/news/
https://libzip.org/download/libzip-1.4.0.tar.xz

I guess "Improve" means something different here.
I'd like a good answer to why anyone should have to patch a build system to support installing libraries to /usr/lib64 on x86_64 systems in 2017, especially when the project in question *just* switched to that build system because it's an "improvement" somehow. Not fussing at you, of course, but geez.
Yes, I filed an issue upstream: https://github.com/nih-at/libzip/issues/19

gmgf 12-29-2017 03:30 PM

Yes I saw that, Robby,

because -DCMAKE_INSTALL_LIBDIR=lib${LIBDIRSUFFIX} not work correctly here.

Alien Bob 12-29-2017 03:41 PM

He already fixed it in git: https://github.com/nih-at/libzip/com...974192a53c7291

rworkman 12-29-2017 03:45 PM

Yep, that was fast. Very nice.

arcctgx 12-30-2017 12:08 PM

I was always wondering about this: why is MPlayer binary dynamically linked with libsmbclient.so? Do we really need this dependency? How common is it to play media from SMB shares over the network?

I don't know if other people consider it a problem. But for me it's inconvenient, because I don't need Samba at all, so I uninstall the package (or don't install it in the first place). But then it's necessary to recompile MPlayer, because it fails to start.

Could this dependency be avoided in MPlayer package shipped with the next Slackware release?

shastah 12-30-2017 12:16 PM

Quote:

Originally Posted by arcctgx (Post 5799715)
I was always wondering about this: why is MPlayer binary dynamically linked with libsmbclient.so? Do we really need this dependency? How common is it to play media from SMB shares over the network?

I don't know if other people consider it a problem. But for me it's inconvenient, because I don't need Samba at all, so I uninstall the package (or don't install it in the first place). But then it's necessary to recompile MPlayer, because it fails to start.

Could this dependency be avoided in MPlayer package shipped with the next Slackware release?

+1 to that

Darth Vader 12-30-2017 12:32 PM

Quote:

Originally Posted by arcctgx (Post 5799715)
I was always wondering about this: why is MPlayer binary dynamically linked with libsmbclient.so? Do we really need this dependency? How common is it to play media from SMB shares over the network?

Believe or not, it is usual for those that have a Linux box at home, to have at least other one running Windows. Hence, the SAMBA is useful for MPlayer.

Just because you personally do NOT use the SAMBA, that does not make it "obsolete".

ponce 12-30-2017 12:33 PM

Quote:

Originally Posted by arcctgx (Post 5799715)
How common is it to play media from SMB shares over the network?

(I speak for me but) here is pretty common.

Darth Vader 12-30-2017 12:34 PM

Quote:

Originally Posted by shastah (Post 5799720)
+1 to that


-1000000
for that. To intentionally broke even those small bits of compatibility with a Windows local network is a freaking bad idea. :p

shastah 12-30-2017 02:13 PM

Quote:

Originally Posted by Darth Vader (Post 5799730)

-1000000
for that. To intentionally broke even those small bits of compatibility with a Windows local network is a freaking bad idea. :p

That's not breaking too much, if you have samba you could still mount a Windows share and use mplayer with that. But there are other ways to do it, one would be to split samba into samba and samba-libs.

I wish mplayer did dlopen() for streams too, like it can do for AV plugins (if compiled with --enable-dynamic-plugins)

orbea 12-30-2017 02:18 PM

Quote:

Originally Posted by arcctgx (Post 5799715)
Could this dependency be avoided in MPlayer package shipped with the next Slackware release?

Just rebuild it yourself, that is what I do with MPlayer since I do not need all the enabled features.

USUARIONUEVO 12-30-2017 02:43 PM

what happen arround enchant 2.x branch ?

Here is enchant-2.2.0
https://github.com/AbiWord/enchant/r...t-2.2.0.tar.gz

dugan 12-30-2017 03:30 PM

Quote:

Originally Posted by arcctgx (Post 5799715)
How common is it to play media from SMB shares over the network?

I'd imagine that a single Windows media server serving media for an entire household (including the Linux users in that household) is an extremely common setup.

rworkman 12-30-2017 04:01 PM

Quote:

Originally Posted by USUARIONUEVO (Post 5799763)
what happen arround enchant 2.x branch ?

Here is enchant-2.2.0
https://github.com/AbiWord/enchant/r...t-2.2.0.tar.gz

Go back and read the first post in this thread.

USUARIONUEVO 12-30-2017 04:05 PM

@rworkman

Sorry , i no see is considering arround plasma5 , waiting then.

Thanks !!

janhe 12-30-2017 05:19 PM

IPv6 and VLAN, yay!
 
Quote:

Originally Posted by rworkman (Post 5798989)
...
TODO items:
* Jakub Jankowski has a seems-to-be-working patch for vlan support in network-scripts; see the "vlan" branch here: https://git.rlworkman.net/slacknetsetup/
* if anyone has some free time and wants a challenge, figure out a way to do ipv6 support such that it integrates nicely and works well; good luck. :-)

I have a slackware box that I have configured as an ipv6 router/tunnel endpoint. I've just finished installing a laptop that is an ipv6 network client.
What do you mean by:
- ipv6 support
- integrates nicely?

The client is configured with one sysctl connfiguration file (and including the ipv6 module in the initrd).
The server (Slackware 13.1) has an extra file in rc.d that sets up the routing (it is called from rc.local):
- open an ipv6 in ipv4 tunnel
- set an ipv6 address on my end of the tunnel
- add an ipv6 address on eth0
- start radvd (router advertisement deamon, from SBo) with its own rc.* script

TLDR: I have a laptop client that already has an ipv6 configuration that IMO integrates nicely, and a server/router whose configuration could be adapted to integrate nicer. I don't know if it would cover all scenarios that you want.

Also, the router has a VLAN that terminates on eth0. I got away with configuring that using only rc.netdevice and rc.inet1.conf. I guess the "vlan" branch will do away with the need for changes in rc.netdevice? I don't see my specific setup in the test scenarios, so if you want I can try if my scenario also works... Scenario is static IP on eth0 and static IP on eth0.4 (eth0 is parent of eth0.4).

I've been away from this forum for a long time, so please forgive (and educate) me if I am missing something obvious.

Drakeo 12-30-2017 06:49 PM

The editor Geany in the extra directory.

Drakeo 12-30-2017 07:05 PM

Quote:

Originally Posted by arcctgx (Post 5799715)
I was always wondering about this: why is MPlayer binary dynamically linked with libsmbclient.so? Do we really need this dependency? How common is it to play media from SMB shares over the network?

I don't know if other people consider it a problem. But for me it's inconvenient, because I don't need Samba at all, so I uninstall the package (or don't install it in the first place). But then it's necessary to recompile MPlayer, because it fails to start.

Could this dependency be avoided in MPlayer package shipped with the next Slackware release?

If I remember right we are using pulseaudio and 14.2 and current build the mplayer with pulseaudio. and that would bring in samba client because you need it for many things.
It is actually a server and works with data bases over the internet. I see a huge reason why it should be a must. With or without pulseaudio. Think of Mplayer it does a ton of stuff like rtmpdump. the sambaclient works direct with mariadb. So many cool things you can do with it and the media now.

bassmadrigal 12-30-2017 09:00 PM

2 Attachment(s)
I know this has been discussed before, but would we be able to change the default output of removepkg to just display the errors of removing files/folders rather than showing every attempt at removing a file and folder? Right now it is extremely difficult to catch any errors while removing a package unless you look over it later or pipe the output to another command. I would love to only see the errors rather than have them mixed in with the rest of the files that were removed as expected. It would make it much easier to clean up any remnants from removed packages.

Right now, you'd have to hope you have a big enough console buffer and scroll up, pipe the output to grep, or save it to a file to comb through it later.

For those who wish to keep the "verbose" output, a -verbose option could remain.

I did a quick patch of -current's removepkg adding this ability. I enabled support for -v, -verbose, or --verbose. See below or attached.

Code:

diff --git a/removepkg b/removepkg
index 127e518..ae5de0a 100755
--- a/removepkg
+++ b/removepkg
@@ -216,7 +216,9 @@ delete_files() {
      echo "WARNING: $ROOT/$FILE changed after package installation."
    fi
    if [ ! "$WARN" = "true" ]; then
-    echo "  --> Deleting $ROOT/$FILE"
+    if [ "$VERBOSE" = "true" ]; then
+      echo "  --> Deleting $ROOT/$FILE"
+    fi
      preserve_file "$FILE" && rm -f "$ROOT/$FILE"
    else
      echo "  --> $ROOT/$FILE would be deleted"
@@ -235,7 +237,9 @@ delete_links() {
  while read LINK ; do
  if [ -L "$ROOT/$LINK" ]; then
    if [ ! "$WARN" = "true" ]; then
-    echo "  --> Deleting symlink $ROOT/$LINK"
+    if [ "$VERBOSE" = "true" ]; then
+    echo "  --> Deleting symlink $ROOT/$LINK"
+    fi
    rm -f "$ROOT/$LINK"
    else
    echo "  --> $ROOT/$LINK (symlink) would be deleted"
@@ -252,7 +256,9 @@ delete_dirs() {
  if [ -d "$ROOT/$DIR" ]; then
    if [ ! "$WARN" = "true" ]; then
      if [ $(ls -a "$ROOT/$DIR" | wc -l) -eq 2 ]; then
-        echo "  --> Deleting empty directory $ROOT/$DIR"
+        if [ "$VERBOSE" = "true" ]; then
+          echo "  --> Deleting empty directory $ROOT/$DIR"
+        fi
        rmdir "$ROOT/$DIR"
      else
        echo "WARNING: Unique directory $ROOT/$DIR contains new files"
@@ -269,7 +275,9 @@ delete_cats() {
  while read FILE ; do
    if [ -f "$ROOT/$FILE" ]; then
      if [ ! "$WARN" = "true" ]; then
-      echo "  --> Deleting $ROOT/$FILE (fmt man page)"
+      if [ "$VERBOSE" = "true" ]; then
+        echo "  --> Deleting $ROOT/$FILE (fmt man page)"
+      fi
        rm -f $ROOT/$FILE
      else
        echo "  --> $ROOT/$FILE (fmt man page) would be deleted"
@@ -362,6 +370,7 @@ remove_packages() {
      mv $ADM_DIR/scripts/$PKGNAME $ADM_DIR/removed_scripts
    fi
    fi
+  echo "Package $PKGNAME removed."
  else
    echo "No such package: $ADM_DIR/packages/$PKGNAME. Can't remove."
  fi
@@ -369,7 +378,7 @@ remove_packages() {
 }

 if [ "$#" = "0" ]; then
-  echo "Usage: $(basename $0) [-copy] [-keep] [-preserve] [-warn] packagename ..."; exit 1
+  echo "Usage: $(basename $0) [-copy] [-keep] [-preserve] [-verbose] [-warn] packagename ..."; exit 1
 fi

 while : ; do
@@ -377,8 +386,9 @@ while : ; do
  -copy | --copy) WARN=true; PRESERVE=true; shift;;
  -keep | --keep) KEEP=true; shift;;
  -preserve | --preserve) PRESERVE=true; shift;;
+  -verbose | --verbose | -v) VERBOSE=true; shift;;
  -warn | --warn) WARN=true; shift;;
-  -* | --*) echo "Usage: $(basename $0) [-copy] [-keep] [-preserve] [-warn] packagename ..."; exit 1;;
+  -* | --*) echo "Usage: $(basename $0) [-copy] [-keep] [-preserve] [-verbose] [-warn] packagename ..."; exit 1;;
  *) break
  esac
 done

Also, there are two minor grammar mistakes that will show if you enable the preserve option. Patch is below (patch is for the unmodified removepkg) and attached.

Code:

diff --git a/removepkg b/removepkg
index 127e518..4c1e49a 100755
--- a/removepkg
+++ b/removepkg
@@ -386,14 +386,14 @@ done
 if [ "$WARN" = "true" ]; then
  echo "Only warning... not actually removing any files."
  if [ "$PRESERVE" = "true" ]; then
-  echo "Package contents is copied to $PRES_DIR."
+  echo "Package contents are copied to $PRES_DIR."
  fi
  echo "Here's what would be removed (and left behind) if you"
  echo "removed the package(s):"
  echo
 else
  if [ "$PRESERVE" = "true" ]; then
-  echo "Package contents is copied to $PRES_DIR."
+  echo "Package contents are copied to $PRES_DIR."
  fi
 fi


chrisretusn 12-30-2017 09:09 PM

Quote:

Originally Posted by bassmadrigal (Post 5799843)
I know this has been discussed before, but would we be able to change the default output of removepkg to just display the errors of removing files/folders rather than showing every attempt at removing a file and folder? Right now it is extremely difficult to catch any errors while removing a package unless you look over it later or pipe the output to another command. I would love to only see the errors rather than have them mixed in with the rest of the files that were removed as expected. It would make it much easier to clean up any remnants from removed packages.

Right now, you'd have to hope you have a big enough console buffer and scroll up, pipe the output to grep, or save it to a file to comb through it later.

For those who wish to keep the "verbose" output, a -verbose option could remain.

I did a quick patch of -current's removepkg adding this ability. I enabled support for -v, -verbose, or --verbose. See below or attached.

I like this idea. For me it matters not what is default but I do like just a displaying errors option, be it default or as an option. Right now I tee the output of upgradepkg, removepkg and slackpkg (when I remember too at least).

orbea 12-30-2017 09:58 PM

I don't like that solution. A better way is to use this function which will redirect any errors/warnings to stderr which can then be filtered out or redirected by the user.

Code:

die () {
  ret="$1"; shift
  printf %s\\n "$@" >&2
  case "$ret" in
    : ) return 0 ;;
    * ) exit "$ret" ;;
  esac
}

It can then be used like this.

Code:

die 1 "This is an error message"
die 0 "This is an exit message"
die : "This is a warning message"

Instead of this.
Code:

echo "This is an error message"; exit 1

Darth Vader 12-30-2017 11:29 PM

Quote:

Originally Posted by Drakeo (Post 5799810)
The editor Geany in the extra directory.

Just wait for That Ugly Lady to enter in the building. ;)

Because the Kate from Plasma 5 is really, but really good (for developing). :D

Alien Bob 12-31-2017 03:48 AM

Quote:

Originally Posted by Darth Vader (Post 5799859)
Because the Kate from Plasma 5 is really, but really good (for developing). :D

Do I hear a grudging approval of Plasma 5?

gmgf 12-31-2017 04:24 AM

xterm-331:

http://invisible-island.net/xterm/xterm.log.html
ftp://ftp.invisible-island.net/xterm/xterm-331.tgz

DarkVision 12-31-2017 04:25 AM

1 Attachment(s)
I think this was already mentioned: xfce4-pulseaudio-plugin-0.3.4

I applied a short patch to fix auto-detection of *bz2 tarballs.
Quote:

Binary files xfce4-pulseaudio-plugin.orig/xfce4-pulseaudio-plugin-0.2.5.tar.xz and xfce4-pulseaudio-plugin/xfce4-pulseaudio-plugin-0.2.5.tar.xz differ
Binary files xfce4-pulseaudio-plugin.orig/xfce4-pulseaudio-plugin-0.3.4.tar.bz2 and xfce4-pulseaudio-plugin/xfce4-pulseaudio-plugin-0.3.4.tar.bz2 differ
diff -U3 -d -r -N xfce4-pulseaudio-plugin.orig/xfce4-pulseaudio-plugin.SlackBuild xfce4-pulseaudio-plugin/xfce4-pulseaudio-plugin.SlackBuild
--- xfce4-pulseaudio-plugin.orig/xfce4-pulseaudio-plugin.SlackBuild 2017-04-26 22:00:48.000000000 +0200
+++ xfce4-pulseaudio-plugin/xfce4-pulseaudio-plugin.SlackBuild 2017-12-31 11:06:59.674000000 +0100
@@ -58,7 +58,7 @@
mkdir -p $TMP $PKG
cd $TMP
rm -rf $PKGNAM-$VERSION
-tar xvf $CWD/$PKGNAM-$VERSION.tar.xz || exit 1
+tar xvf $CWD/$PKGNAM-$VERSION.tar.?z* || exit 1
cd $PKGNAM-$VERSION || exit 1
chown -R root:root .
find . \

shastah 12-31-2017 04:27 AM

When kernel 4.14 lands in main tree eventually, I suggest putting a note in ChangeLog.txt/UPGRADE.TXT/CHANGES_AND_HINTS.TXT about the fact that "cciss" driver is now removed in favor of "hpsa" (which supports all boards cciss did and is actually a module alias for cciss now). Disks connected to previously-cciss will still be visible, but if one refers to them as /dev/cciss/... (ie. in /etc/fstab) it will no longer work. Also smartctl/smartd needs some tuning, you need to know which scsi generic device your controller is at (lsscsi -g), and then point smartd there:
Code:

$ lsscsi -g
[0:1:0:0]    disk    HP      LOGICAL VOLUME  7.24  /dev/sda  /dev/sg0
[0:1:0:1]    disk    HP      LOGICAL VOLUME  7.24  /dev/sdb  /dev/sg1
[0:3:0:0]    storage HP      P400i            7.24  -          /dev/sg2
$
$ grep sg2 /etc/smartd.conf
/dev/sg2 -d cciss,0 -I 190 -a -m root
/dev/sg2 -d cciss,1 -I 190 -a -m root
/dev/sg2 -d cciss,2 -I 190 -a -m root
/dev/sg2 -d cciss,3 -I 190 -a -m root
/dev/sg2 -d cciss,4 -I 190 -a -m root
$

This may affect people running Slackware on HP servers.

DarkVision 12-31-2017 04:36 AM

BTW: I maintain my own plasma5 packages for more then three years now, independently from AlienBobs packages. I use Plasma5 as my default DE on my desktop and on my Lenovo-ThinkPad. And in my opinion it just "works". I really would like to see a list of issues that would make Plasma5 a "showstopper" for Slackware15... and "High-memory-usage" does not really count.

dugan 12-31-2017 04:42 PM

Does ctags really need to be part of the vim package?

I'd prefer it if it were its own package, to make it easier to replace with Universal Ctags.

atelszewski 12-31-2017 05:26 PM

Hi,

And maybe xxd could have its own package?
Then I wouldn't have to install this pesky vim thing at all ;->

--
Best regards,
Andrzej Telszewski

Drakeo 12-31-2017 08:36 PM

Quote:

Originally Posted by Darth Vader (Post 5799859)
Just wait for That Ugly Lady to enter in the building. ;)

Because the Kate from Plasma 5 is really, but really good (for developing). :D

I got hooked on it when playing with puppy Linux before slacko pups it is a cool tool.
Think current has everything in it to build it now.

TurboBlaze 01-01-2018 04:23 AM

scangearmp2
https://github.com/Ordissimo/scangearmp2

simple-scan
https://gitlab.gnome.org/GNOME/simple-scan

epson-inkjet-printer-escpr (Last Updated: 2017-12-29 14:37)
https://aur.archlinux.org/packages/e...printer-escpr/
+ https://download3.ebz.epson.net/dsc/...1lsb3.2.tar.gz
+ bug_x86_64.patch !!!
+ https://slackbuilds.org/repository/1...printer-escpr/
>>> epson-inkjet-printer-escpr-1.6.18-x86_64-1_SBo.tgz

cups-bjnp-2.0
https://sourceforge.net/projects/cup...les/cups-bjnp/
https://slackbuilds.org/repository/1...tem/cups-bjnp/
>>> cups-bjnp-2.0-x86_64-1_SBo.tgz


All times are GMT -5. The time now is 08:06 PM.