public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Maciej Barć" <xgqt@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-scheme/chez/
Date: Tue, 29 Aug 2023 20:03:31 +0000 (UTC)	[thread overview]
Message-ID: <1693339408.a4110d24a8191476173d0aeb779ff36133cf72cc.xgqt@gentoo> (raw)

commit:     a4110d24a8191476173d0aeb779ff36133cf72cc
Author:     Maciej Barć <xgqt <AT> gentoo <DOT> org>
AuthorDate: Tue Aug 29 19:41:15 2023 +0000
Commit:     Maciej Barć <xgqt <AT> gentoo <DOT> org>
CommitDate: Tue Aug 29 20:03:28 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a4110d24

dev-scheme/chez: bump to 9.6.0

Signed-off-by: Maciej Barć <xgqt <AT> gentoo.org>

 dev-scheme/chez/Manifest          |  1 +
 dev-scheme/chez/chez-9.6.0.ebuild | 75 +++++++++++++++++++++++++++++++++++++++
 2 files changed, 76 insertions(+)

diff --git a/dev-scheme/chez/Manifest b/dev-scheme/chez/Manifest
index 568283eb5c15..ca167efd0cff 100644
--- a/dev-scheme/chez/Manifest
+++ b/dev-scheme/chez/Manifest
@@ -1,2 +1,3 @@
 DIST chez-9.5.8.tar.gz 35487100 BLAKE2B 6c5467f812788166aded14ce38ec2935bb890f2386f3ea7ec29a97c6a3d9aa37f26960e44aa6acd6b3954e45dfc4eaff4fc7db1dd77b231fb380a1dac7349be4 SHA512 80a4e9f61ddb254bef1a249af1d32f918df88390946fbe6eeb62c3510c760bf899285be1aba70eda9b54bcb0c6fef3fe7deace648993cd9cece2d08cf0ade9c0
 DIST chez-9.5.8a.tar.gz 35488602 BLAKE2B 49facf50d7cbd301257cd2a0e180cd9ef0608241e599f56a29146fb64bc5f49c1ee536ef70d35f249baa2ba00721f2b28ff1256e3b0ccaf3fbfe426995aaae52 SHA512 64ede117b8e91b7f9f5203899d9063b3638fdaaeaef30afd5a020c41d3c3f3625772a3cb9fed68850926dffe543d2f6c6e4259845f7fd09bee9479afa35bf653
+DIST chez-9.6.0.tar.gz 35690840 BLAKE2B 2669f7f4f1086e43ab6b4904992b7ffc743bdfa2466c01e0e5e1e4cfdbf01f2e6dcf65c759f7543c9a42ff8d769fa337a7280245d7eca57e379d3087b3095c02 SHA512 268aa93b32a970b564c17726cdcca177c1f589fc49b88b30dd2c6aedbbd7c13dbb0bd421cc80d10b6ef84f0170c54ac329f04c2571910a012d759b2489a2aed5

diff --git a/dev-scheme/chez/chez-9.6.0.ebuild b/dev-scheme/chez/chez-9.6.0.ebuild
new file mode 100644
index 000000000000..6cce9c186365
--- /dev/null
+++ b/dev-scheme/chez/chez-9.6.0.ebuild
@@ -0,0 +1,75 @@
+# Copyright 2021-2023 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+inherit toolchain-funcs
+
+DESCRIPTION="A programming language based on R6RS"
+HOMEPAGE="https://cisco.github.io/ChezScheme/ https://github.com/cisco/ChezScheme"
+SRC_URI="https://github.com/cisco/ChezScheme/releases/download/v${PV}/csv${PV//a}.tar.gz
+	-> ${P}.tar.gz"
+S="${WORKDIR}"/csv${PV//a}
+
+# Chez Scheme itself is Apache 2.0, but it vendors Nanopass and stex
+# which are both MIT licensed.
+LICENSE="Apache-2.0 MIT"
+SLOT="0/${PV}"
+KEYWORDS="~amd64 ~x86"
+IUSE="X ncurses threads"
+
+BDEPEND="virtual/pkgconfig"
+RDEPEND="
+	app-arch/lz4:=
+	sys-apps/util-linux
+	sys-libs/zlib:=
+	ncurses? ( sys-libs/ncurses:= )
+"
+DEPEND="${RDEPEND}"
+RDEPEND="
+	${RDEPEND}
+	X? ( x11-libs/libX11 )
+"
+
+src_prepare() {
+	tc-export AR CC CXX LD RANLIB
+
+	default
+
+	if use ncurses ; then
+		local nclibs="\"$($(tc-getPKG_CONFIG) --libs ncurses)\""
+		sed -i "s|ncursesLib=-lncurses|ncursesLib=${nclibs}|g" configure || die
+	fi
+
+	# Remove -Werror
+	sed -i "/^C = /s|-Werror||g" c/Mf-* || die
+}
+
+src_configure() {
+	local myconfargs=(
+		$(usex threads '--threads' '')
+		$(usex ncurses '' '--disable-curses')
+		$(usex X '' '--disable-x11')
+		--installprefix="/usr"
+		--installbin="/usr/bin"
+		--installlib="/usr/$(get_libdir)"
+		--installman="/usr/share/man"
+		--installschemename=chezscheme
+		--installpetitename=chezscheme-petite
+		--installscriptname=chezscheme-script
+		--libkernel
+		--nogzip-man-pages
+		LZ4=$($(tc-getPKG_CONFIG) --libs liblz4)
+		ZLIB=$($(tc-getPKG_CONFIG) --libs zlib)
+	)
+	sh ./configure "${myconfargs[@]}" || die
+}
+
+src_install() {
+	# TempRoot == DESTDIR
+	emake TempRoot="${D}" install
+	einstalldocs
+
+	find "${ED}"/usr/$(get_libdir)/csv${PV//a}/examples \
+		 \( -name "*.md" -o -name "*.so" \)  -delete || die
+}


             reply	other threads:[~2023-08-29 20:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29 20:03 Maciej Barć [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-31 17:51 [gentoo-commits] repo/gentoo:master commit in: dev-scheme/chez/ Matthew Smith
2024-06-29 10:47 Maciej Barć
2024-05-23 22:08 Maciej Barć
2024-03-13 16:40 Maciej Barć
2024-03-13 16:40 Maciej Barć
2024-03-13 12:05 Arthur Zamarin
2024-02-07 22:21 Maciej Barć
2024-01-03  2:20 Ionen Wolkens
2023-12-08  0:29 Maciej Barć
2023-10-18 22:05 Maciej Barć
2023-10-17 13:39 Maciej Barć
2023-10-17 13:39 Maciej Barć
2023-10-01 18:07 Arthur Zamarin
2023-08-30 18:29 Maciej Barć
2023-08-30 18:29 Maciej Barć
2023-08-29 20:03 Maciej Barć
2023-07-11  8:43 Jakov Smolić
2023-04-27 23:00 Maciej Barć
2023-04-26 21:25 Maciej Barć
2022-08-25 16:23 Maciej Barć
2022-08-16 19:43 Sam James
2022-07-16  7:52 Matthew Smith
2022-07-16  7:52 Matthew Smith
2022-05-29  7:22 Jakov Smolić
2022-04-25 21:35 Maciej Barć
2022-03-26 17:19 Maciej Barć
2022-02-16 11:34 Maciej Barć
2022-02-16 10:50 Maciej Barć
2021-12-27  9:52 Jakov Smolić
2021-12-13 19:53 Maciej Barć
2021-11-25 18:18 Maciej Barć

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=1693339408.a4110d24a8191476173d0aeb779ff36133cf72cc.xgqt@gentoo \
    --to=xgqt@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