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] [Closed]: snapcast: update to 0.28.0
Date: Mon, 17 Jun 2024 01:09:47 +0200	[thread overview]
Message-ID: <20240616230947.2E0B92BC47@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50290@inbox.vuxu.org>

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

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

snapcast: update to 0.28.0
https://github.com/void-linux/void-packages/pull/50290

Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

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

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->

This release no longer bundles the pre-built [Snapweb](https://github.com/badaix/snapweb). When accessing the Snapweb page, you are now greeted with the following notice.
```
This is a placeholder for Snapweb, a web based control client and player for Snapcast.
To install Snapweb, please follow these steps:

    1. Download Snapweb on the Snapweb release page. You can either download
        * snapweb.zip and extract it on your Snapcast server machine, e.g. into /usr/share/snapserver/snapweb or
        * snapweb_x.y.z-1_all.deb and install it with sudo apt install ./snapweb_x.y.z-1_all.deb to /usr/share/snapweb
    2. Configure the document root (doc_root, see below) in the snapserver configuration file snapserver.conf — usually located in /etc/snapserver.conf — to the location where snapweb is extracted or installed.
    3. Restart Snapserver to activate the changes: sudo service snapserver restart
```
What should we do with Snapweb?
1. Leave the `snapcast` package as is and let the user fetch and extract the pre-built Snapweb as per instructions.
2. Fetch and install the pre-built Snapweb from the `snapserver` subpackage.
3. Create a new `snapweb` package and build it from source. The user can then install it if needed.

      parent reply	other threads:[~2024-06-16 23:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-12  5:09 [PR PATCH] " amak79
2024-05-12  5:13 ` [PR PATCH] [Updated] " amak79
2024-05-12  5:20 ` the-maldridge
2024-05-12  6:21 ` amak79
2024-05-21  5:03 ` [PR PATCH] [Updated] " amak79
2024-05-21  5:21 ` amak79
2024-05-21  5:45 ` amak79
2024-06-16 23:09 ` 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=20240616230947.2E0B92BC47@inbox.vuxu.org \
    --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).