Github messages for voidlinux
 help / color / mirror / Atom feed
From: Logarithmus <Logarithmus@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pulseeffects: update to 5.0.4 & fix greyed-out effects
Date: Sat, 26 Jun 2021 17:26:42 +0200	[thread overview]
Message-ID: <20210626152642.GGrJYdylFagrrhCx2mLNP1sRNxieVNq2-FjSHzgz11M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31663@inbox.vuxu.org>

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

New comment by Logarithmus on void-packages repository

https://github.com/void-linux/void-packages/pull/31663#issuecomment-869018297

Comment:
Because `pkgconf` is faster and better in any way: http://pkgconf.org/features.html

On Sat, 2021-06-26 at 08:24 -0700, Michal Vasilek wrote:
> @paper42 commented on this pull request.
> 
> In srcpkgs/pulseeffects-legacy/template:
> > @@ -4,18 +4,16 @@ version=4.8.5
>  revision=1
>  wrksrc="pulseeffects-${version}"
>  build_style=meson
> -hostmakedepends="itstool pkg-config gettext"
> +hostmakedepends="itstool pkgconf gettext"
> why?
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or unsubscribe.




  parent reply	other threads:[~2021-06-26 15:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-26 15:12 [PR PATCH] " Logarithmus
2021-06-26 15:24 ` paper42
2021-06-26 15:24 ` [PR REVIEW] " paper42
2021-06-26 15:26 ` Logarithmus [this message]
2021-06-26 15:27 ` Logarithmus
2021-06-26 15:27 ` Logarithmus
2021-06-26 15:28 ` [PR REVIEW] " paper42
2021-06-26 15:29 ` Logarithmus
2021-06-26 15:30 ` Logarithmus
2021-06-26 15:31 ` paper42
2021-06-26 15:31 ` [PR REVIEW] " Logarithmus
2021-06-26 15:35 ` Logarithmus
2021-06-26 15:35 ` Logarithmus
2021-06-26 15:38 ` [PR PATCH] [Closed]: " Logarithmus
2021-06-26 15:39 ` meator
2021-06-26 16:37 ` Logarithmus
2021-06-26 16:38 ` Logarithmus

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=20210626152642.GGrJYdylFagrrhCx2mLNP1sRNxieVNq2-FjSHzgz11M@z \
    --to=logarithmus@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).