Requests for -current (14.2-->15.0)

almope · 01-27-2022, 05:30 PM

Quote:

Originally Posted by LuckyCyborg

Did you literally tried this, and it really builds this way, producing meaningful support for those JACK things?

I ask because I'm under impression that the PipeWire uses the JACK libraries (and headers) for the associated JACK support.

Yes, I've been testing this with jack applications. I can imagine the headers are pretty identical, but the libraries are pipewires implemention.
It seems to work great so far. I've only used qjackctl, carla, faust2jack program and done simple recording though.

Being able to route alsa, pulse and jack streams around between devices and programs, in just one place (qjackctl) is really nice. IMHO.

almope · 01-27-2022, 05:39 PM

Quote:

Originally Posted by volkerdi

Doing so installs files that would conflict with a system jack package such as the one SBo's SlackBuild produces.

Yes. But then again, maybe a system jack package is never even needed.

camerabambai · 01-27-2022, 06:12 PM

Quote:

Originally Posted by Nobby6

Today ISC is pleased to announce the release of BIND 9.18.0

This is the first stable release that contains support for DoT and DoH.

This new release of BIND is available for download from the Internet
Systems Consortium web site (https://www.isc.org/downloads)

Significant work covered in the 9.18.0 branch includes:

- Support for securing DNS traffic using Transport Layer Security (TLS).
TLS is used by both DNS-over-TLS (DoT) and DNS-over-HTTPS (DoH).
- Support for zone transfers over TLS (XFR-over-TLS, XoT) for both
incoming and outgoing zone transfers.
- The dig tool is now able to send DoT queries (+tls option).
- Support for OpenSSL 3.0 APIs was added.

You can read more about this new edition of BIND in the release notes:

9.18.0: https://downloads.isc.org/isc/bind9/...nd-9.18.0.html

The feature of DOT is really interesting, I know is easy to setup (as client) using systemd-resolver, but for Slackware which don't have the systemd? Network manager and standard /etc/resolv.conf support DOT ?

Tshane · 01-27-2022, 06:38 PM

Quote:

Originally Posted by camerabambai

The feature of DOT is really interesting, I know is easy to setup (as client) using systemd-resolver, but for Slackware which don't have the systemd? Network manager and standard /etc/resolv.conf support DOT ?

I have not looked at how easy it is to configure but I built 9.18 yesterday, built fine, runs fine, the only compatibility issue would be anyone running rndc over a socket, and not localhost, but I've never seen a configuration like that anyway so would be very rare, I think with shiny new slackware coming it would be ideal time to up to 9.18, I've not setup DoT, because I don't live in a country where everyone spies on your DNS or logs it.

DoT DoH is all smoke and mirrors since your DoH server is likely looking in plain text to every server in that chain, including any forwarders.

drgibbon · 01-27-2022, 08:55 PM

scratch that.

LuckyCyborg · 01-28-2022, 01:06 AM

Mr. Volkerding,

please bee kind to ship with the Mesa package also the eglinfo program found (and anyway built) on mesa-demos.

For convenience:

Code:

--- mesa.SlackBuild.orig	2021-10-15 20:58:59.704019723 +0300
+++ mesa.SlackBuild	2022-01-28 08:59:51.511308250 +0200
@@ -183,7 +183,7 @@
     make install DESTDIR=$PKG/cruft || exit 1
     # Install gears and glinfo, as well as a few other demos:
     mkdir -p $PKG/usr/bin
-    for demo in gears glinfo glthreads glxcontexts glxdemo glxgears \
+    for demo in eglinfo gears glinfo glthreads glxcontexts glxdemo glxgears \
       glxgears_fbconfig glxheads glxinfo glxpbdemo glxpixmap ; do
       mv --verbose $PKG/cruft/usr/bin/$demo $PKG/usr/bin
   done

This eglinfo is a tool like glinfo or glxinfo, but for EGL.

Honestly, I have noticed its absence by playing with the Info Center from Plasma 5.24 Beta, which uses it to display a page for OpenGL (EGL), as seen in the attached screenshots.

However, I do not think that its utility is limited at a future release of KDE Plasma.

qunying · 01-28-2022, 12:38 PM

Quote:

Originally Posted by almope

Yes, I've been testing this with jack applications. I can imagine the headers are pretty identical, but the libraries are pipewires implemention.
It seems to work great so far. I've only used qjackctl, carla, faust2jack program and done simple recording though.

Being able to route alsa, pulse and jack streams around between devices and programs, in just one place (qjackctl) is really nice. IMHO.

According to the INSTALL.md from pipewire

Code:

### JACK emulation

PipeWire reimplements the 3 libraries that JACK applications use to make
them run on top of PipeWire.

These libraries are found here:

```
/usr/lib64/pipewire-0.3/jack/libjacknet.so -> libjacknet.so.0
/usr/lib64/pipewire-0.3/jack/libjacknet.so.0 -> libjacknet.so.0.304.0
/usr/lib64/pipewire-0.3/jack/libjacknet.so.0.304.0
/usr/lib64/pipewire-0.3/jack/libjackserver.so -> libjackserver.so.0
/usr/lib64/pipewire-0.3/jack/libjackserver.so.0 -> libjackserver.so.0.304.0
/usr/lib64/pipewire-0.3/jack/libjackserver.so.0.304.0
/usr/lib64/pipewire-0.3/jack/libjack.so -> libjack.so.0
/usr/lib64/pipewire-0.3/jack/libjack.so.0 -> libjack.so.0.304.0
/usr/lib64/pipewire-0.3/jack/libjack.so.0.304.0

```

The provided pw-jack script uses LD_LIBRARY_PATH to set the library
search path to these replacement libraries. This allows you to run
jack apps on both the real JACK server or on PipeWire with the script.

It is also possible to completely replace the JACK libraries by adding
a file `pipewire-jack-x86_64.conf` to `/etc/ld.so.conf.d/` with
contents like:

```
/usr/lib64/pipewire-0.3/jack/
```

Note that when JACK is replaced by PipeWire, the SPA JACK plugin (installed
in /usr/lib64/spa-0.2/jack/libspa-jack.so) is not useful anymore and
distributions should make them conflict.

To avoid the bootstrap requirement of a jack package, I used the following patch to build:

Code:

--- pipewire-0.3.44/spa/meson.build     2022-01-27 01:17:53.000000000 -0800
+++ pipewire-new/spa/meson.build        2022-01-28 10:06:41.670127795 -0800
@@ -56,8 +56,6 @@
     summary({'AAC': fdk_aac_dep.found()}, bool_yn: true, section: 'Bluetooth audio codecs')
   endif
   avcodec_dep = dependency('libavcodec', required: get_option('ffmpeg'))
-  jack_dep = dependency('jack', version : '>= 1.9.10', required: get_option('jack'))
-  summary({'JACK2': jack_dep.found()}, bool_yn: true, section: 'Backend')
   vulkan_dep = dependency('vulkan', disabler : true, version : '>= 1.1.69', required: get_option('vulkan'))
   vulkan_headers = cc.has_header('vulkan/vulkan.h', dependencies : vulkan_dep)
   #summary({'Vulkan': vulkan_headers}, bool_yn: true, section: 'Misc dependencies')
--- pipewire-0.3.44/spa/plugins/meson.build     2022-01-27 01:17:53.000000000 -0800
+++ pipewire-new/spa/plugins/meson.build        2022-01-28 10:06:09.726125952 -0800
@@ -19,9 +19,6 @@
 if avcodec_dep.found()
   subdir('ffmpeg')
 endif
-if jack_dep.found()
-  subdir('jack')
-endif
 if not get_option('support').disabled()
   subdir('support')
 endif

The I install the ld.conf file to make pipewire-jack always visible.

PS. this build of pipewire would be in conflict with SBo jack package, they could not coexist.

USUARIONUEVO · 01-28-2022, 12:58 PM

I request jack several times, but ever ignored , its required by big number or libs/apps under slackware stock packages and under sb0 , rebuild stocj slackware packages to get advantages is not a good thing.

I wait for next release cycle.

USUARIONUEVO · 01-28-2022, 12:59 PM

Quote:

Originally Posted by qunying

According to the INSTALL.md from pipewire
PS. this build of pipewire would be in conflict with SBo jack package, they could not coexist.

Nice , destroy all jack compatibility under SBo , nice , really nice /ironic off here

The locigal movement here its include jack on stock slackware and rebuild things to cath it , but this not go to succes now. RC3

LuckyCyborg · 01-28-2022, 01:15 PM

Quote:

Originally Posted by USUARIONUEVO

Nice , destroy all jack compatibility under SBo , nice , really nice /ironic off here

Yeah, some day Slackware may will choose to have PipeWire as default media server and exactly this will happen.

Not now, not yet, BUT you seen a glimpse of future things to happen. I may call you a visionary.

Anyway, I believe that talking about those obsolete things like are PulseAudio or JACK is just like talking about Da Vinci's inventions.

Great things at their time, I agree! BUT the World moves to future. Evolves. Always.

USUARIONUEVO · 01-28-2022, 01:33 PM

Quote:

Originally Posted by LuckyCyborg

Yeah, some day Slackware may will choose to have PipeWire as default media server and exactly this will happen.

Not now, BUT you seen a glimpse of future things to happen. I may call you a visionary.

Anyway, I believe that talking about those obsolete things like are PulseAudio or JACK is just like talking about Da Vinci's inventions.

Great things at their time, I agree! BUT the World moves to future. Evolves. Always.

jack is old thing , OKEY , but pipewire wants , why ?

A very large of things can benefit including jack , like ffmpeg , gst-plugins-good , pulse ...

Im not have personal interest in jack , but things can be done only in two ways , the correct one , and all others.

As ever you understand 0 , if this change break jack from sbo , then all slackbuilds depend on it go to be broj=ken , only to make happy some people , i think this is bad.

LuckyCyborg · 01-28-2022, 01:46 PM

Quote:

Originally Posted by USUARIONUEVO

jack is old thing , OKEY , but pipewire wants , why ?

A very large of things can benefit including jack , like ffmpeg , gst-plugins-good , pulse ...

Im not have personal interest in jack , but things can be done only in two ways , the correct one , and all others.

As ever you understand 0 , if this change break jack from sbo , then all slackbuilds depend on it go to be broj=ken , only to make happy some people , i think this is bad.

Is not about making me happy, even I do not care less about JACK.

It's about the Linux movement to a universal audio/video solution, which is PipeWire. They wanted this and they made this.

Because both PulseAudio and JACK failed to become this solution, at least in the audio side. PulseAudio is for "customers" while JACK is for "professionals" and this resulted in a huge fragmentation on software ecosystem for Linux.

Both PulseAudio and JACK support present on PipeWire is just for compatibility, to not force the developers to move all suddenly to the native PipeWire API.

BUT, more and more software will move to the native PipeWire API in the years to come, and I suspect that in the next 5 - 6 years (which I suspect that will be the next development cycle of Slackware), probably all maintained audio/video software will use directly the PipeWire API, with no need for those compat APIs for PulseAudio or JACK.

True, there would be also "victims" as in the software which is abandonware.

And, do NOT worry! I bet that SBo will adapt. They always adapt.

bassmadrigal · 01-28-2022, 01:50 PM

Quote:

Originally Posted by LuckyCyborg

in the next 5 - 6 years (which I suspect that will be the next development cycle of Slackware)

I *REALLY* hope it is not that long. I hope this was just a one-off and not an indication of the future Slackware release cycles.

marav · 01-28-2022, 02:01 PM

Quote:

Originally Posted by bassmadrigal

I *REALLY* hope it is not that long. I hope this was just a one-off and not an indication of the future Slackware release cycles.

1-year-release, like from 13.0 to 14.1 will be great

qunying · 01-28-2022, 04:13 PM

No, it does not destroy all jack compatibility under SBo, all packages depends on jack could be build without problem with pipewire-jack/dev enabled. It only in conflict with the jack package itself, as both provide the same header and libraries.

So you either build a pipewire without jack and have the SBo jack package or with pipewire-jack and remove the SBo jack. The pipewire-jack's header and libraries are suppose binary compatible with jack itself.

Quote:

Originally Posted by USUARIONUEVO

Nice , destroy all jack compatibility under SBo , nice , really nice /ironic off here

The locigal movement here its include jack on stock slackware and rebuild things to cath it , but this not go to succes now. RC3