import waypipe-0.8.2-1.el9

c9-beta imports/c9-beta/waypipe-0.8.2-1.el9
CentOS Sources 2022-09-27 08:29:38 -04:00 committed by Stepan Oksanichenko
parent 3d734c639c
commit e3156c6b18
4 changed files with 21 additions and 13 deletions

.gitignore vendored
View File

@ -1 +1 @@

View File

@ -1 +1 @@
d3a74b2d7853e93fa0cd991b7bac2f4b04b65ece SOURCES/waypipe-v0.8.0.tar.gz
813882a89f6067337e4e7286e127a4a09c69a939 SOURCES/waypipe-v0.8.2.tar.gz

View File

@ -1,11 +1,11 @@
.\" Generated by scdoc 1.11.1
.\" Generated by scdoc 1.11.2
.\" Complete documentation for this program is not available as a GNU info page
.ie \n(.g .ds Aq \(aq
.el .ds Aq '
.ad l
.\" Begin generated content:
.TH "waypipe" "1" "2021-04-03"
.TH "waypipe" "1" "2022-04-05"
@ -67,10 +67,12 @@ compressible as images containing pictures.\&
.RS 4
Select the compression method applied to data transfers.\& Options are
\fInone\fR (for high-bandwidth networks), \fIlz4\fR (intermediate), \fIzstd\fR
(slow connection).\& The default compression is \fInone\fR.\& The compression
(slow connection).\& The default compression is \fInone\fR.\& The compression
level can be chosen by appending = followed by a number.\& For example,
if \fBC\fR is \fIzstd=7\fR, waypipe will use level 7 Zstd compression.\&
† In a future version, the default will change to \fIlz4\fR.\&
\fB-d, --debug\fR
.RS 4
@ -103,7 +105,10 @@ both the client and the server for their socket paths.\&
.RS 4
Print the version number and quit.\&
Briefly describe Waypipe'\&s version and the features it was built with,
then quit.\& Possible features: LZ4 compression support, ZSTD compression
support, ability to transfer DMABUFs, video compression support, VAAPI
hardware video de/encoding support.\&
@ -119,7 +124,7 @@ when they are available.\&
.RS 4
For server or ssh mode, provide the path to the "control pipe" that will
be created the the server.\& Writing (with \fBwaypipe recon C T\fR, or
'echo -n T > C') a new socket path to this pipe will make the server
\&'\&echo -n T > C'\&) a new socket path to this pipe will make the server
instance replace all running connections with connections to the new
Unix socket.\& The new socket should ultimately forward data to the same
waypipe client that the server was connected to before.\&
@ -254,10 +259,10 @@ to connect to \fIremote\fR from computer \fIlocal\fR:
.RS 4
$ waypipe --socket /tmp/waypipe-remote\&.sock client &
$ ncat --ssl -lk 12345 --sh-exec 'ncat -U /tmp/waypipe-remote\&.sock' &
$ ncat --ssl -lk 12345 --sh-exec \&'ncat -U /tmp/waypipe-remote\&.sock\&' &
$ ssh user@remote
> ncat -lkU /tmp/waypipe-local\&.sock --sh-exec 'ncat --ssl local 12345' &
> ncat -lkU /tmp/waypipe-local\&.sock --sh-exec \&'ncat --ssl local 12345\&' &
> waypipe --display wayland-local \\
--socket /tmp/waypipe-local\&.sock server -- sleep inf &
> WAYLAND_DISPLAY=wayland-local application
@ -265,7 +270,7 @@ to connect to \fIremote\fR from computer \fIlocal\fR:
Given a certificate file, socat can also provide an encrypted connection
(remove 'verify=0' to check certificates):
(remove '\&verify=0'\& to check certificates):
.RS 4
@ -281,7 +286,7 @@ Given a certificate file, socat can also provide an encrypted connection
Many applications require specific environment variables to use Wayland instead
of X11.\& If ssh isn't configured to support loading \fI~/.\&ssh/environment\fR,
of X11.\& If ssh isn'\&t configured to support loading \fI~/.\&ssh/environment\fR,
one can use \fIenv\fR to set the needed variables each time; or run waypipe without
a command, to use the login shell environment.\&

View File

@ -1,6 +1,6 @@
Name: waypipe
Version: 0.8.0
Release: 2%{?dist}
Version: 0.8.2
Release: 1%{?dist}
Summary: Wayland forwarding proxy
License: MIT
@ -57,6 +57,9 @@ install -m 644 %{SOURCE1} %{buildroot}%{_mandir}/man1/
* Tue May 17 2022 Olivier Fourdan <> - 0.8.2-1
- Update to 0.8.2 (#2071907)
* Tue Aug 10 2021 Mohan Boddu <> - 0.8.0-2
- Rebuilt for IMA sigs, glibc 2.34, aarch64 flags
Related: rhbz#1991688