Github messages for voidlinux
 help / color / mirror / Atom feed
From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] usbredir: update to 0.13.0.
Date: Mon, 10 Jul 2023 16:49:13 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44963@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 570 bytes --]

There is a new pull request by motorto against master on the void-packages repository

https://github.com/motorto/void-packages usbredir-0.13.0
https://github.com/void-linux/void-packages/pull/44963

usbredir: update to 0.13.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**


#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc

A patch file from https://github.com/void-linux/void-packages/pull/44963.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-usbredir-0.13.0-44963.patch --]
[-- Type: text/x-diff, Size: 1477 bytes --]

From d68dc642c150ab94150b6e9836a23cd0c6d1247f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Mon, 10 Jul 2023 15:48:42 +0100
Subject: [PATCH] usbredir: update to 0.13.0.

---
 srcpkgs/usbredir/template | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/usbredir/template b/srcpkgs/usbredir/template
index af1e9d69de0e..2471a702bd55 100644
--- a/srcpkgs/usbredir/template
+++ b/srcpkgs/usbredir/template
@@ -1,9 +1,9 @@
 # Template file for 'usbredir'
 pkgname=usbredir
-version=0.10.0
+version=0.13.0
 revision=1
 build_style=meson
-configure_args="--sbindir=/usr/bin -Ddefault_library=both"
+configure_args="-Db_lto=true"
 hostmakedepends="pkg-config"
 makedepends="libusb-devel glib-devel"
 short_desc="USB traffic redirection protocol"
@@ -11,14 +11,13 @@ maintainer="Andrea Brancaleoni <abc@pompel.me>"
 license="GPL-2.0-or-later"
 homepage="https://spice-space.org"
 distfiles="https://gitlab.freedesktop.org/spice/usbredir/-/archive/usbredir-${version}/usbredir-usbredir-${version}.tar.bz2"
-checksum=10143222c3ab3333252b546954cd3ee14bebe657c4e94e07ddef7071007cb7d1
+checksum=f8281022a7ede923b532dd1f869e5348898d44ccf1ccb4af22e8bf20810d9737
 
 usbredir-devel_package() {
 	depends="${makedepends} ${sourcepkg}-${version}_${revision}"
 	short_desc+=" - development files"
 	pkg_install() {
 		vmove usr/include
-		vmove "usr/lib/*.a"
 		vmove "usr/lib/*.so"
 		vmove usr/lib/pkgconfig
 	}

             reply	other threads:[~2023-07-10 14:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 14:49 motorto [this message]
2023-07-10 14:50 ` [PR PATCH] [Updated] " motorto
2023-07-10 14:53 ` motorto
2023-07-10 14:58 ` motorto
2023-07-10 20:54 ` classabbyamp
2023-07-10 22:18 ` motorto
2023-08-06  3:57 ` [PR PATCH] [Merged]: " classabbyamp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44963@inbox.vuxu.org \
    --to=motorto@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).