public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Pacho Ramos" <pacho@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/trinity/
Date: Thu,  4 Jan 2018 10:37:33 +0000 (UTC)	[thread overview]
Message-ID: <1515062240.158f19e4ea24315601e245376031c7aa3edaa2f7.pacho@gentoo> (raw)

commit:     158f19e4ea24315601e245376031c7aa3edaa2f7
Author:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
AuthorDate: Thu Jan  4 10:34:20 2018 +0000
Commit:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
CommitDate: Thu Jan  4 10:37:20 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=158f19e4

dev-util/trinity: Version bump

Package-Manager: Portage-2.3.19, Repoman-2.3.6

 dev-util/trinity/Manifest           |  1 +
 dev-util/trinity/trinity-1.8.ebuild | 41 +++++++++++++++++++++++++++++++++++++
 2 files changed, 42 insertions(+)

diff --git a/dev-util/trinity/Manifest b/dev-util/trinity/Manifest
index 5e658d2441c..8e0ae95bb9f 100644
--- a/dev-util/trinity/Manifest
+++ b/dev-util/trinity/Manifest
@@ -1 +1,2 @@
 DIST trinity-1.7.tar.xz 195488 BLAKE2B a2efd5fa2dd9ae40e943d96b2ae9232e292bb5cd41a350813a137a5910cf308a06d4e0b1be37e2ab8dc6325443101b6d956a593a778d9a7128e086ebbf6f2b61 SHA512 bb702ec79494591e04c74279e39d6dd0c5779f7cb2696c306c94bee3a8aefb524e369674daadf02f70b58dbb19ad5699d2c331bc4c9089046d2214403a95ba87
+DIST trinity-1.8.tar.xz 213984 BLAKE2B 56f664023e2bc3648e941e4a3cb20e450cdcad3556289e201513d1755267eb013da2be035e81c87b3f1d1b0b1e12cb041c6bb345f7a84ee4c5c12f20a8e87f55 SHA512 686076dab2346cf9b5d8a20b14db31f460a352fa72eeadbe005a7423941918f5afef08b4987bb68cbbf4218d0cb620adb85f8036294d8df5ab5262e0031a44e4

diff --git a/dev-util/trinity/trinity-1.8.ebuild b/dev-util/trinity/trinity-1.8.ebuild
new file mode 100644
index 00000000000..1072988366e
--- /dev/null
+++ b/dev-util/trinity/trinity-1.8.ebuild
@@ -0,0 +1,41 @@
+# Copyright 1999-2018 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=6
+inherit toolchain-funcs
+
+DESCRIPTION="A Linux system call fuzz tester"
+HOMEPAGE="http://codemonkey.org.uk/projects/trinity/"
+SRC_URI="http://codemonkey.org.uk/projects/${PN}/${P}.tar.xz"
+
+LICENSE="GPL-2"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+IUSE="examples"
+
+# We need newer headers to avoid compilation failures in the BPF stuff.
+DEPEND="app-arch/xz-utils
+	>=sys-kernel/linux-headers-4.8
+"
+
+src_configure() {
+	tc-export CC
+	default
+}
+
+src_compile() {
+	# Enable a verbose (i.e. not quiet) build.
+	emake V=1
+}
+
+src_install() {
+	dobin "${PN}"
+	dodoc Documentation/*
+	einstalldocs
+
+	if use examples ; then
+		exeinto "/usr/share/doc/${PF}/scripts"
+		doexe scripts/*
+		docompress -x "/usr/share/doc/${PF}/scripts"
+	fi
+}


             reply	other threads:[~2018-01-04 10:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 10:37 Pacho Ramos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-04-14 15:19 [gentoo-commits] repo/gentoo:master commit in: dev-util/trinity/ Andrew Savchenko
2018-10-20 12:17 Pacho Ramos
2016-04-05 18:02 Patrice Clement
2016-04-02  9:21 David Seifert
2015-09-15  0:41 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=1515062240.158f19e4ea24315601e245376031c7aa3edaa2f7.pacho@gentoo \
    --to=pacho@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