Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions [bot] <"github-actions [bot]"@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: shairport-sync-classic-4.3.2
Date: Tue, 19 Mar 2024 02:44:59 +0100	[thread overview]
Message-ID: <20240319014459.E976F2B91F@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47596@inbox.vuxu.org>

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

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

New package: shairport-sync-classic-4.3.2
https://github.com/void-linux/void-packages/pull/47596

Description:
Implementation of an Airplay 1 audio receiver. [Homepage](https://github.com/mikebrady/shairport-sync).

Note: the source can be built into either an Airplay 1 or Airplay 2 receiver. The Airplay 2 version is packaged as another package `shairport-sync-airplay2`. Both packages provide the alternative `shairport-sync:/usr/bin/shairport-sync`.

The application supports virtually all audio systems, and it builds with support for ALSA, Pulse, JACK, and PipeWire by default (audio systems available in the Void repos). It does not build with Unix pipe output support -- (imo) use cases for this should be handled by the user's audio system instead.

I've been using this package for ~a year on Pulse and PipeWire now without issue.

Needs [alac](https://github.com/void-linux/void-packages/pull/47597) to build.

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

#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**

#### Local build testing
- I built this PR locally for my native architecture, `x86_64-glibc`
- I built this PR locally for these architectures:
  - aarch64-musl
  - aarch64
  - armv7l-musl
  - armv7l
  - armv6l-musl
  - armv6l


      parent reply	other threads:[~2024-03-19  1:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 14:42 [PR PATCH] " misterupkeep
2023-12-05 14:52 ` ahesford
2023-12-05 14:54 ` ahesford
2023-12-05 14:57 ` misterupkeep
2023-12-05 14:59 ` ahesford
2024-03-05  1:44 ` github-actions
2024-03-19  1:44 ` github-actions [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=20240319014459.E976F2B91F@inbox.vuxu.org \
    --to=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).