From: "Conrad Kostecki" <conikost@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lua/luacheck/
Date: Fri, 25 Nov 2022 17:59:17 +0000 (UTC) [thread overview]
Message-ID: <1669399118.705c6e4403bbd771b8b174f34ec395e1ad235566.conikost@gentoo> (raw)
commit: 705c6e4403bbd771b8b174f34ec395e1ad235566
Author: Conrad Kostecki <conikost <AT> gentoo <DOT> org>
AuthorDate: Fri Nov 25 17:58:38 2022 +0000
Commit: Conrad Kostecki <conikost <AT> gentoo <DOT> org>
CommitDate: Fri Nov 25 17:58:38 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=705c6e44
dev-lua/luacheck: add 1.0.0
Signed-off-by: Conrad Kostecki <conikost <AT> gentoo.org>
dev-lua/luacheck/Manifest | 1 +
dev-lua/luacheck/luacheck-1.0.0.ebuild | 66 ++++++++++++++++++++++++++++++++++
2 files changed, 67 insertions(+)
diff --git a/dev-lua/luacheck/Manifest b/dev-lua/luacheck/Manifest
index 82e17824b0a5..1e78ef845f84 100644
--- a/dev-lua/luacheck/Manifest
+++ b/dev-lua/luacheck/Manifest
@@ -1 +1,2 @@
DIST luacheck-0.25.0.tar.gz 162675 BLAKE2B 143de767f004cb485abc4952eafc4d02c16ca4d421397d0179113ddaeacc2cd7ba2b4b8eed48f9a05169c5e20ae53aaef8c5253ab1d7c7e4b178218fab0e03d6 SHA512 7f9f02464cb40462c321dd23e32263913ead2bf4eace6907d51a5b570a6a19a378b12660c98e63ca447cfc507dfb491d54b093af3962f12596a7c6088c8dc867
+DIST luacheck-1.0.0.tar.gz 177029 BLAKE2B f56315663f571c71944e4739956eb45600cfc324cbc6914a65ac45a6923f49cba7201bde18390d7ce7a374aa561680de05988c3a283c936658d1cda18f8f6b24 SHA512 f6703fb1b72b8ff8dd4b15bb1e5f7fa81607ee13505fd927e427f0b1043949c5dbc014020759dd8b63ec2013698b4086e773625bc925568970787c8e40e282cd
diff --git a/dev-lua/luacheck/luacheck-1.0.0.ebuild b/dev-lua/luacheck/luacheck-1.0.0.ebuild
new file mode 100644
index 000000000000..95aeb8ab6707
--- /dev/null
+++ b/dev-lua/luacheck/luacheck-1.0.0.ebuild
@@ -0,0 +1,66 @@
+# Copyright 1999-2022 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+LUA_COMPAT=( lua5-{1..4} luajit )
+
+inherit lua toolchain-funcs
+
+DESCRIPTION="A tool for linting and static analysis of Lua code"
+HOMEPAGE="https://github.com/lunarmodules/luacheck"
+SRC_URI="https://github.com/lunarmodules/luacheck/archive/refs/tags/v${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ia64 ~ppc ~ppc64 ~riscv ~sparc ~x86"
+IUSE="doc test"
+RESTRICT="!test? ( test )"
+
+RDEPEND="
+ dev-lua/lua-argparse[${LUA_USEDEP}]
+ dev-lua/lua-utf8[${LUA_USEDEP}]
+ dev-lua/luafilesystem[${LUA_USEDEP}]
+"
+
+DEPEND="${RDEPEND}"
+
+BDEPEND="
+ virtual/pkgconfig
+ doc? ( dev-python/sphinx )
+ test? (
+ dev-lua/busted[${LUA_USEDEP}]
+ dev-lua/lua_cliargs[${LUA_USEDEP}]
+ ${RDEPEND}
+ )
+"
+
+PATCHES=( "${FILESDIR}/${PN}-0.23.0-disable-measuring-performance-test.patch" )
+
+src_compile() {
+ if use doc; then
+ sphinx-build docsrc html || die
+ fi
+}
+
+lua_src_test() {
+ busted --lua=${ELUA} || die
+}
+
+src_test() {
+ lua_foreach_impl lua_src_test
+}
+
+lua_src_install() {
+ insinto "$(lua_get_lmod_dir)"
+ doins -r src/luacheck
+}
+
+src_install() {
+ lua_foreach_impl lua_src_install
+
+ newbin bin/luacheck.lua luacheck
+
+ use doc && local -a HTML_DOCS=( "html/." )
+ einstalldocs
+}
next reply other threads:[~2022-11-25 17:59 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 17:59 Conrad Kostecki [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-27 15:40 [gentoo-commits] repo/gentoo:master commit in: dev-lua/luacheck/ Conrad Kostecki
2024-06-27 15:40 Conrad Kostecki
2024-05-24 23:35 Conrad Kostecki
2024-01-14 2:39 Conrad Kostecki
2024-01-14 2:39 Conrad Kostecki
2023-12-12 22:16 Conrad Kostecki
2023-12-12 22:16 Conrad Kostecki
2023-07-26 0:55 Sam James
2023-06-24 21:36 Conrad Kostecki
2023-01-31 15:17 Conrad Kostecki
2023-01-31 15:17 Conrad Kostecki
2022-12-20 22:03 Conrad Kostecki
2022-12-20 22:03 Conrad Kostecki
2022-03-12 11:54 Conrad Kostecki
2022-03-12 11:54 Conrad Kostecki
2021-09-18 12:29 Marek Szuba
2021-05-25 16:21 Georgy Yakovlev
2021-04-22 19:31 Sergei Trofimovich
2021-04-21 21:03 Conrad Kostecki
2021-04-20 21:20 Sergei Trofimovich
2021-04-16 21:29 Conrad Kostecki
2021-04-16 21:29 Conrad Kostecki
2021-04-16 21:29 Conrad Kostecki
2021-03-16 17:37 Conrad Kostecki
2021-01-27 19:48 Conrad Kostecki
2021-01-11 8:01 Sam James
2021-01-09 16:22 Sam James
2020-12-17 14:17 Conrad Kostecki
2020-12-17 13:53 Conrad Kostecki
2020-12-17 13:09 Conrad Kostecki
2020-12-17 13:09 Conrad Kostecki
2020-12-17 12:48 Sam James
2020-12-03 13:50 Marek Szuba
2020-12-03 5:04 Sam James
2020-11-30 13:33 Conrad Kostecki
2020-11-29 17:11 Sergei Trofimovich
2020-11-29 1:37 Conrad Kostecki
2020-11-29 1:33 Conrad Kostecki
2020-11-29 1:33 Conrad Kostecki
2020-11-29 1:33 Conrad Kostecki
2020-11-29 1:33 Conrad Kostecki
2020-09-04 23:31 Sam James
2020-03-15 23:36 Georgy Yakovlev
2020-03-15 23:31 Georgy Yakovlev
2020-03-15 23:31 Georgy Yakovlev
2019-07-29 14:41 Mikle Kolyada
2019-05-24 22:51 Sergei Trofimovich
2019-05-24 22:08 Sergei Trofimovich
2019-05-12 20:56 Thomas Deutschmann
2018-07-07 12:15 Jonas Stein
2018-04-21 22:56 Aaron Bauman
2018-04-21 16:00 Mikle Kolyada
2018-04-01 11:48 Mikle Kolyada
2018-03-27 8:06 Sergei Trofimovich
2018-03-27 7:31 Sergei Trofimovich
2017-09-02 8:45 Michał Górny
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=1669399118.705c6e4403bbd771b8b174f34ec395e1ad235566.conikost@gentoo \
--to=conikost@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