From: "Miroslav Šulc" <fordfrog@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-sound/chuck/
Date: Sat, 04 Jan 2025 11:48:02 +0000 (UTC) [thread overview]
Message-ID: <1735991279.1db3da46c8197d5e0a04278b6b1fb698547c506e.fordfrog@gentoo> (raw)
commit: 1db3da46c8197d5e0a04278b6b1fb698547c506e
Author: Miroslav Šulc <fordfrog <AT> gentoo <DOT> org>
AuthorDate: Sat Jan 4 11:47:49 2025 +0000
Commit: Miroslav Šulc <fordfrog <AT> gentoo <DOT> org>
CommitDate: Sat Jan 4 11:47:59 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1db3da46
media-sound/chuck: bump to 1.5.4.4
Signed-off-by: Miroslav Šulc <fordfrog <AT> gentoo.org>
media-sound/chuck/Manifest | 1 +
media-sound/chuck/chuck-1.5.4.4.ebuild | 70 ++++++++++++++++++++++++++++++++++
2 files changed, 71 insertions(+)
diff --git a/media-sound/chuck/Manifest b/media-sound/chuck/Manifest
index 42ec64d969b4..60cd0d93202c 100644
--- a/media-sound/chuck/Manifest
+++ b/media-sound/chuck/Manifest
@@ -1,2 +1,3 @@
DIST chuck-1.5.4.2.tgz 22311827 BLAKE2B 1215211c837fa55c132742a9a4edef97446304fffb6a6e9f4de0d1da66c634c81398870fbd30ba864939f7e3a54bd0f2125bd6c4c9634edb51da43fa25fd05a9 SHA512 c4ce1e3e04d33fbd516f41eebfbc3b71399c587c0ea7b5d16b4d8a8fe5efb3e244ea0e8860f7331aa740f68f96f6b8f92d37104e6b71f0b6e0cb704acc14715b
DIST chuck-1.5.4.3.tgz 22318954 BLAKE2B 83fffaa811fb9ba73f2000ea7a6d5e133c42964571340877a4080e2a6360ac3a7df8bda01a7c0a4acbdbe2f64d97310dbcff237d935b5598ba5ca0e1a312cd2f SHA512 a8324c7dcd5d031cc256d0a5e87d69ae728d008735c81d977911695ec9e93ff6e647cbc4ef36f7fabf84674c468fcaf7df3350f4898436267344f44f8e4089c7
+DIST chuck-1.5.4.4.tgz 22334080 BLAKE2B 84d3a9e11205c95695fc2b1e9af9fccb31d9a7f2dd6f4184c8bd3b9425cbdb05dac36d477cb6aeb6e757299dc972e2daff5b18d7f5fd748d3c31e04974dd70b9 SHA512 725bea6ee81443e0d65eac80746d2600bf5ab0db2495e8eb376851f46da413ad954106fb9da15b440250da335f0ae63f624945e338a9b2136c110ea876464a05
diff --git a/media-sound/chuck/chuck-1.5.4.4.ebuild b/media-sound/chuck/chuck-1.5.4.4.ebuild
new file mode 100644
index 000000000000..cf941b17862c
--- /dev/null
+++ b/media-sound/chuck/chuck-1.5.4.4.ebuild
@@ -0,0 +1,70 @@
+# Copyright 1999-2025 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+inherit flag-o-matic toolchain-funcs
+
+DESCRIPTION="Strongly-timed, concurrent, and on-the-fly audio programming language"
+HOMEPAGE="http://chuck.cs.princeton.edu/"
+SRC_URI="http://chuck.cs.princeton.edu/release/files/${P}.tgz"
+
+LICENSE="GPL-2"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+IUSE="+alsa jack examples"
+REQUIRED_USE="|| ( alsa jack )"
+
+RDEPEND="app-eselect/eselect-chuck
+ media-libs/libsndfile
+ alsa? ( media-libs/alsa-lib )
+ jack? ( virtual/jack )"
+DEPEND="${RDEPEND}
+ app-alternatives/yacc
+ app-alternatives/lex"
+
+PATCHES=(
+ "${FILESDIR}"/${PN}-1.4.0.0-hid-smc.patch
+ "${FILESDIR}"/${PN}-1.5.3.2-makefile.patch
+)
+
+compile_backend() {
+ backend=$1
+ pushd "${S}/src" &>/dev/null || die
+ einfo "Compiling against ${backend}"
+ emake CC="$(tc-getCC)" CXX="$(tc-getCXX)" LD="$(tc-getCXX)" linux-${backend}
+ mv chuck{,-${backend}} || die
+ emake clean
+ popd &>/dev/null || die
+}
+
+src_compile() {
+ # when compile with athlon or athlon-xp flags
+ # chuck crashes on removing a shred with a double free or corruption
+ # it happens in Chuck_VM_Stack::shutdown() on the line
+ # SAFE_DELETE_ARRAY( stack );
+ replace-cpu-flags athlon athlon-xp i686
+
+ use jack && compile_backend jack
+ use alsa && compile_backend alsa
+}
+
+src_install() {
+ use jack && dobin src/chuck-jack
+ use alsa && dobin src/chuck-alsa
+
+ dodoc AUTHORS DEVELOPERS QUICKSTART README.md THANKS VERSIONS
+ if use examples; then
+ dodoc -r examples
+ docompress -x /usr/share/doc/${PF}/examples
+ fi
+}
+
+pkg_postinst() {
+ if [[ -z ${REPLACING_VERSIONS} ]]; then
+ elog "Chuck now can use multiple audio engines, so you can specify"
+ elog "the preferred audio engine with chuck-{jack,alsa}"
+ elog "Or you can use 'eselect chuck' to set the audio engine"
+ fi
+ eselect chuck update --if-unset
+}
next reply other threads:[~2025-01-04 11:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 11:48 Miroslav Šulc [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-20 18:37 [gentoo-commits] repo/gentoo:master commit in: media-sound/chuck/ Miroslav Šulc
2025-04-19 18:02 Miroslav Šulc
2025-02-08 9:13 Miroslav Šulc
2025-02-06 22:03 Sam James
2025-02-06 22:03 Sam James
2025-01-05 17:49 Arthur Zamarin
2025-01-05 17:49 Arthur Zamarin
2025-01-01 16:01 Miroslav Šulc
2024-12-30 1:09 Sam James
2024-12-30 1:09 Sam James
2024-12-06 9:59 Sam James
2024-12-06 9:59 Sam James
2024-12-06 9:20 Miroslav Šulc
2024-11-24 9:24 Miroslav Šulc
2024-11-05 9:48 Miroslav Šulc
2024-11-03 8:36 Miroslav Šulc
2022-07-22 7:49 Agostino Sarubbo
2022-07-22 7:43 Agostino Sarubbo
2022-05-21 6:25 Miroslav Šulc
2022-03-19 23:45 Sam James
2021-07-29 8:20 Miroslav Šulc
2021-07-29 7:08 Agostino Sarubbo
2021-07-29 6:45 Agostino Sarubbo
2021-06-27 9:36 Miroslav Šulc
2021-05-28 15:57 David Seifert
2020-09-05 15:15 Sam James
2020-09-02 8:57 Miroslav Šulc
2020-08-02 12:27 Miroslav Šulc
2018-11-09 0:43 Andreas Sturmlechner
2018-09-05 21:18 Andreas Sturmlechner
2016-08-07 8:37 Tim Harder
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=1735991279.1db3da46c8197d5e0a04278b6b1fb698547c506e.fordfrog@gentoo \
--to=fordfrog@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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