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/)

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.


All times are GMT -5. The time now is 07:37 PM.