Github messages for voidlinux
 help / color / mirror / Atom feed
From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: spotifyd: add build_options
Date: Tue, 05 May 2020 22:13:12 +0200	[thread overview]
Message-ID: <20200505201312.HOE6aG7t-ZA1lsX0BjwmtnDnUqTD2kq2MxDGc9UdikY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21446@inbox.vuxu.org>

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

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

spotifyd: add build_options
https://github.com/void-linux/void-packages/pull/21446

Description:
Instead of manually altering the Cargo.toml file, we use the feature
flags available in cargo. There are three build options now:

- alsa: ALSA backend
- pulseaudio: Pulseaudio backend
- dbus: D-Bus functionality, both mpris and keyring

This also allows for a greater granularity when specifying dependencies.
All build options are selected as default, both to keep the package the
same as it was before (alsa and pulseaudio) and because the dependency
needed by the dbus option (dbus-libs) is required by pulseaudio already.

This commit allows builders to easily disable D-Bus functionality or
either audio backend without altering the template.

--

Removing the dbus option as a default one would be ok too.

I'd also like to leave the template as an idea for how to start implementing the feature flags straight into the cargo build style.

@abenson can you review this one, please?

Also, the aarch64-musl error still happens, unfortunately, but is supposed to have been fixed in a next version of the `nix` crate. So perhaps when there's a next release we can re-enable the package for that arch as well.

      parent reply	other threads:[~2020-05-05 20:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21446@inbox.vuxu.org>
2020-04-29 21:37 ` jnbr
2020-04-30 23:26 ` [PR PATCH] [Updated] " ericonr
2020-04-30 23:28 ` ericonr
2020-05-01  1:07 ` [PR PATCH] [Updated] " ericonr
2020-05-01 22:19 ` ericonr
2020-05-02 13:09 ` ericonr
2020-05-02 13:12 ` ericonr
2020-05-05 20:13 ` abenson [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=20200505201312.HOE6aG7t-ZA1lsX0BjwmtnDnUqTD2kq2MxDGc9UdikY@z \
    --to=abenson@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).