Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: libspnav: update to 1.1, minor fixes
Date: Sun, 25 Jun 2023 20:07:35 +0200	[thread overview]
Message-ID: <20230625180735.PPuGbgHGO2iPAVft2v5rlRZAC78lXq6LC3e2NLSApzU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44552@inbox.vuxu.org>

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

There's a merged pull request on the void-packages repository

libspnav: update to 1.1, minor fixes
https://github.com/void-linux/void-packages/pull/44552

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

Using a SpaceMouse Pro Wireless with the latest upstream versions of `spacenavd`, `spnavcfg`, and the latest version of FreeCAD in the repository.

![libspnav-1 1-test-spacemouse-pro-wireless](https://github.com/void-linux/void-packages/assets/4819590/652ba122-021a-4f17-954d-7243073f1f2e)

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

#### Notes

* The upstream sources are now accessible on GitHub (for all three related packages). The 1.1 version is not on SourceForge so I switched the `distfiles` to GitHub.
* I dropped the `do_build()` section as it doesn't seem to be necessary when using the `gnu-configure` build style. If there's something I missed here for why this should be kept in please let me know.
* The library supports a non-X11 build but I'm not sure how to expose that. Does XBPS support variants like that? If it matters to someone and you can point me to the relevant documentation I would be willing to add it.
* I plan to package `spacenavd` and `spnavcfg` next which will depend on this library.


      parent reply	other threads:[~2023-06-25 18:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21 17:41 [PR PATCH] " CtrlC-Root
2023-06-21 17:42 ` CtrlC-Root
2023-06-21 19:00 ` [PR PATCH] [Updated] " CtrlC-Root
2023-06-21 19:00 ` CtrlC-Root
2023-06-24 19:26 ` [PR REVIEW] " classabbyamp
2023-06-25 13:33 ` CtrlC-Root
2023-06-25 13:34 ` [PR PATCH] [Updated] " CtrlC-Root
2023-06-25 13:34 ` [PR REVIEW] " CtrlC-Root
2023-06-25 13:36 ` CtrlC-Root
2023-06-25 13:38 ` [PR PATCH] [Updated] " CtrlC-Root
2023-06-25 13:39 ` [PR REVIEW] " CtrlC-Root
2023-06-25 18:07 ` classabbyamp [this message]

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=20230625180735.PPuGbgHGO2iPAVft2v5rlRZAC78lXq6LC3e2NLSApzU@z \
    --to=classabbyamp@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).