From: "Sam Jorna" <wraeth@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/bats/
Date: Sat, 30 Apr 2016 14:34:53 +0000 (UTC) [thread overview]
Message-ID: <1462026838.50d8d91f5889bdd4b664835067dbc56212b11333.wraeth@gentoo> (raw)
commit: 50d8d91f5889bdd4b664835067dbc56212b11333
Author: Sam Jorna <wraeth <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 30 11:57:33 2016 +0000
Commit: Sam Jorna <wraeth <AT> gentoo <DOT> org>
CommitDate: Sat Apr 30 14:33:58 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=50d8d91f
dev-util/bats: new package
Bats is a TAP-compliant testing framework for Bash. It provides a simple
way to verify that the UNIX programs you write behave as expected.
This has been added in order to support app-admin/yadm in bug 581118.
Maintainer assigned to Espen H per request under Proxy Maintainers.
Gentoo-bug: 581392
Package-Manager: portage-2.2.28
dev-util/bats/Manifest | 1 +
dev-util/bats/bats-0.4.0.ebuild | 24 ++++++++++++++++++++++++
dev-util/bats/metadata.xml | 26 ++++++++++++++++++++++++++
3 files changed, 51 insertions(+)
diff --git a/dev-util/bats/Manifest b/dev-util/bats/Manifest
new file mode 100644
index 0000000..f74b43f
--- /dev/null
+++ b/dev-util/bats/Manifest
@@ -0,0 +1 @@
+DIST bats-0.4.0.tar.gz 17258 SHA256 480d8d64f1681eee78d1002527f3f06e1ac01e173b761bc73d0cf33f4dc1d8d7 SHA512 83c6c0e3ceec149708a8db5d33e95cc84852d8189498c22131c00f4288a6c870f9d522bae9230157f442338dc101e1468451d78dfa274afb83a6f0dd614c8bdb WHIRLPOOL 9617418d6a288d6e57aa1d715498c9adcfbe80cd97a814382431203dab778f26139dc31a14aecfd6f2e71a51f11fe189fce6e3bb7174ce9d4ad25782a9a6fce0
diff --git a/dev-util/bats/bats-0.4.0.ebuild b/dev-util/bats/bats-0.4.0.ebuild
new file mode 100644
index 0000000..3fa4d97
--- /dev/null
+++ b/dev-util/bats/bats-0.4.0.ebuild
@@ -0,0 +1,24 @@
+# Copyright 1999-2016 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Id$
+
+EAPI=6
+
+DESCRIPTION="An automated testing system for bash"
+HOMEPAGE="https://github.com/sstephenson/bats/"
+SRC_URI="https://github.com/sstephenson/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+
+src_test() {
+ bin/bats --tap test
+}
+
+src_install() {
+ einstalldocs
+
+ dobin libexec/*
+ doman man/bats.1 man/bats.7
+}
diff --git a/dev-util/bats/metadata.xml b/dev-util/bats/metadata.xml
new file mode 100644
index 0000000..63003cd
--- /dev/null
+++ b/dev-util/bats/metadata.xml
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+ <maintainer type="person">
+ <email>dev+gentoobugzilla@henriksen.is</email>
+ <name>Espen H</name>
+ <description>Proxy maintainer - set to assignee on bugs</description>
+ </maintainer>
+ <maintainer type="project">
+ <email>proxy-maint@gentoo.org</email>
+ <name>Proxy Maintainers</name>
+ </maintainer>
+ <upstream>
+ <remote-id type="github">sstephenson/bats</remote-id>
+ </upstream>
+ <longdescription lang="en">
+ Bats is a TAP-compliant testing framework for Bash. It provides a simple
+ way to verify that the UNIX programs you write behave as expected.
+
+ A Bats test file is a Bash script with special syntax for defining test
+ cases. Under the hood, each test case is just a function with a description.
+
+ Bats is most useful when testing software written in Bash, but you can use
+ it to test any UNIX program.
+ </longdescription>
+</pkgmetadata>
next reply other threads:[~2016-04-30 14:35 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 14:34 Sam Jorna [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-01 2:08 [gentoo-commits] repo/gentoo:master commit in: dev-util/bats/ Sam Jorna
2017-08-08 11:03 Amy Liffey
2017-08-11 8:55 Lars Wendler
2017-08-11 8:55 Lars Wendler
2018-02-01 6:53 Lars Wendler
2018-02-11 10:53 Michał Górny
2018-10-03 5:15 Georgy Yakovlev
2020-03-31 7:18 Agostino Sarubbo
2020-03-31 7:23 Georgy Yakovlev
2020-03-31 10:01 Agostino Sarubbo
2020-07-28 7:05 Lars Wendler
2020-07-28 7:05 Lars Wendler
2020-07-28 7:05 Lars Wendler
2020-07-28 7:05 Lars Wendler
2020-11-02 1:14 Georgy Yakovlev
2020-11-24 6:06 Georgy Yakovlev
2021-01-03 1:18 Sam James
2021-01-03 1:22 Sam James
2021-01-03 1:22 Sam James
2021-03-16 21:28 Sam James
2021-06-02 10:39 Sam James
2021-07-22 22:25 Marek Szuba
2021-07-29 10:46 Joonas Niilola
2021-07-29 10:46 Joonas Niilola
2021-08-15 14:46 Joonas Niilola
2021-08-15 14:46 Joonas Niilola
2021-09-25 2:58 Sam James
2021-09-25 2:58 Sam James
2021-10-24 4:06 Sam James
2021-11-19 6:18 Arthur Zamarin
2022-01-11 13:01 Jakov Smolić
2022-02-07 11:10 Florian Schmaus
2022-02-25 9:48 Yixun Lan
2022-03-15 16:27 Sam James
2022-03-18 12:26 Arthur Zamarin
2022-03-27 2:33 Sam James
2022-05-05 12:01 Jakov Smolić
2022-06-03 7:52 Joonas Niilola
2022-06-03 7:52 Joonas Niilola
2022-10-01 5:06 Sam James
2022-10-01 5:36 Sam James
2022-10-28 13:40 Florian Schmaus
2023-01-07 11:30 Arthur Zamarin
2023-01-28 9:34 Joonas Niilola
2023-02-24 15:09 Joonas Niilola
2023-03-31 16:21 Arthur Zamarin
2023-05-13 3:31 Sam James
2023-08-11 6:11 Joonas Niilola
2023-10-17 6:00 Joonas Niilola
2023-10-18 12:50 Florian Schmaus
2024-04-22 10:17 Sam James
2024-06-06 17:28 Arthur Zamarin
2024-07-07 21:11 Eli Schwartz
2024-07-07 21:11 Eli Schwartz
2024-12-05 15:17 Florian Schmaus
2025-01-24 7:14 Joonas Niilola
2025-02-16 16:27 Sam James
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=1462026838.50d8d91f5889bdd4b664835067dbc56212b11333.wraeth@gentoo \
--to=wraeth@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