From: not-chicken <not-chicken@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package Request: spek
Date: Tue, 24 Mar 2020 08:23:52 +0100 [thread overview]
Message-ID: <20200324072352.b1Z0DfM9LhkatJLuVaEjXajz7JhhiyK9ZCrkIG6h1Q8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20314@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
New comment by not-chicken on void-packages repository
https://github.com/void-linux/void-packages/issues/20314#issuecomment-603071908
Comment:
It doesn't build because it needs patches to build with latest ffmpeg.
This fork is better suited for inclusion imo : https://github.com/withmorten/spek-alternative
```
# Template file for 'spek-alternative'
pkgname=spek-alternative
version=0.8.2.3
revision=1
build_style=gnu-configure
hostmakedepends="pkg-config automake intltool libtool"
makedepends="ffmpeg-devel gettext-devel wxWidgets-devel"
depends="ffmpeg"
short_desc="Acoustic spectrum analyser"
maintainer="Kartik Singh <kartik.ynwa@gmail.com>"
license="GPL-3.0-or-later"
homepage="https://github.com/withmorten/spek-alternative"
distfiles="https://github.com/withmorten/spek-alternative/archive/${version}.tar.gz"
checksum="007ba4b84a310b078e378aa84c8e80783db5821437a757a488c3ecec377e6b2a"
pre_configure() {
./autogen.sh
}
```
Built and run on x86_64
next prev parent reply other threads:[~2020-03-24 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 11:18 [ISSUE] " kartikynwa
2020-03-24 7:23 ` not-chicken [this message]
2020-03-25 6:12 ` kartikynwa
2020-03-25 6:12 ` [ISSUE] [CLOSED] " kartikynwa
2020-09-10 14:04 [ISSUE] Package request: Spek absolutelynothinghere
2020-09-10 15:33 ` hippi777
2020-09-12 5:33 ` not-chicken
2020-09-12 21:31 ` absolutelynothinghere
2020-12-30 10:31 ` tibequadorian
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=20200324072352.b1Z0DfM9LhkatJLuVaEjXajz7JhhiyK9ZCrkIG6h1Q8@z \
--to=not-chicken@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).