From: "Jeroen Roovers" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/i2c-tools/
Date: Fri, 15 Dec 2017 06:59:32 +0000 (UTC) [thread overview]
Message-ID: <1513321170.3f427ebeb449b638a30deee93d87a27fa57b63aa.jer@gentoo> (raw)
commit: 3f427ebeb449b638a30deee93d87a27fa57b63aa
Author: Jeroen Roovers <jer <AT> gentoo <DOT> org>
AuthorDate: Fri Dec 15 06:59:13 2017 +0000
Commit: Jeroen Roovers <jer <AT> gentoo <DOT> org>
CommitDate: Fri Dec 15 06:59:30 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3f427ebe
sys-apps/i2c-tools: Version bump.
Package-Manager: Portage-2.3.18, Repoman-2.3.6
sys-apps/i2c-tools/Manifest | 1 +
sys-apps/i2c-tools/i2c-tools-4.0.ebuild | 62 +++++++++++++++++++++++++++++++++
2 files changed, 63 insertions(+)
diff --git a/sys-apps/i2c-tools/Manifest b/sys-apps/i2c-tools/Manifest
index aba4e2c12ad..a21d52b725b 100644
--- a/sys-apps/i2c-tools/Manifest
+++ b/sys-apps/i2c-tools/Manifest
@@ -1 +1,2 @@
DIST i2c-tools-3.1.1.tar.bz2 71789 BLAKE2B 0a7a3db6a3b396cfb8d5e58d8c83cae4e52239786502c6552d971350f7fc05a1ce9d7d89e9cdb154a21ac15bdf34aa0dec9501ea45317ec9c5d9fc211780bbf1 SHA512 b91f89b803e5558d49ce63f42f6542438f4f47927e4ce420cd9df989cab14a5c55d971befed73e8f793b0cf4aa41936c0ef519e5a407dceb2c08964461e803c5
+DIST i2c-tools-4.0.tar.xz 79972 BLAKE2B 982e4139ed0e2111f9e082d0690fcc0f86f97a433e292e9464b41991f14a1f90147a3612172bad6880f0df6896612e1dea0ae7bf6f459758b2cff45fb35a5dc7 SHA512 ddf86c357c101388193581bc40285089e6ab5e8d870f8aa5d594acc7ecb8596fbd30501e147b88bdea0200b1be88bc0a374356c188d1bcb067bf8e254e3dc51e
diff --git a/sys-apps/i2c-tools/i2c-tools-4.0.ebuild b/sys-apps/i2c-tools/i2c-tools-4.0.ebuild
new file mode 100644
index 00000000000..44fc1345dfa
--- /dev/null
+++ b/sys-apps/i2c-tools/i2c-tools-4.0.ebuild
@@ -0,0 +1,62 @@
+# Copyright 1999-2017 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=6
+
+PYTHON_COMPAT=( python{2_7,3_4,3_5,3_6} )
+DISTUTILS_OPTIONAL="1"
+
+inherit flag-o-matic multilib toolchain-funcs distutils-r1
+
+DESCRIPTION="I2C tools for bus probing, chip dumping, EEPROM decoding, and more"
+HOMEPAGE="https://www.kernel.org/pub/software/utils/i2c-tools"
+SRC_URI="${HOMEPAGE}/${P}.tar.xz"
+
+LICENSE="GPL-2"
+SLOT="0"
+KEYWORDS="~amd64 ~arm ~arm64 ~mips ~ppc ~ppc64 ~sparc ~x86"
+IUSE="python"
+REQUIRED_USE="python? ( ${PYTHON_REQUIRED_USE} )"
+
+RDEPEND="!<sys-apps/lm_sensors-3
+ python? ( ${PYTHON_DEPS} )"
+DEPEND="${RDEPEND}"
+
+src_prepare() {
+ default
+ use python && distutils-r1_src_prepare
+}
+
+src_configure() {
+ use python && distutils-r1_src_configure
+}
+
+src_compile() {
+ emake all-lib CC=$(tc-getCC) # parallel make
+ emake CC=$(tc-getCC)
+ emake -C eepromer CC=$(tc-getCC)
+ if use python ; then
+ cd py-smbus || die
+ append-cppflags -I../include
+ distutils-r1_src_compile
+ fi
+}
+
+src_install() {
+ emake install libdir=$(get_libdir) prefix="${D}"/usr
+ dosbin eepromer/eeprom{,er}
+ rm -rf "${D}"/usr/include # part of linux-headers
+ dodoc CHANGES README
+ local d
+ for d in eeprom eepromer ; do
+ docinto ${d}
+ dodoc ${d}/README*
+ done
+
+ if use python ; then
+ cd py-smbus || die
+ docinto py-smbus
+ dodoc README*
+ distutils-r1_src_install
+ fi
+}
next reply other threads:[~2017-12-15 6:59 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 6:59 Jeroen Roovers [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-08 5:40 [gentoo-commits] repo/gentoo:master commit in: sys-apps/i2c-tools/ Sam James
2025-03-05 11:40 Sam James
2025-02-24 11:21 Petr Vaněk
2024-05-29 12:15 Sam James
2024-05-28 20:49 Sam James
2024-05-28 20:49 Sam James
2024-05-27 16:14 Joonas Niilola
2024-04-22 17:20 Viorel Munteanu
2024-04-22 16:52 Viorel Munteanu
2024-04-22 16:52 Viorel Munteanu
2023-02-23 13:45 Andrew Ammerlaan
2022-11-15 18:22 Michał Górny
2022-08-28 5:06 WANG Xuerui
2022-05-07 17:50 Arthur Zamarin
2022-05-07 13:20 Jakov Smolić
2022-05-07 10:56 Jakov Smolić
2022-05-07 10:56 Jakov Smolić
2022-05-07 10:05 Arthur Zamarin
2022-05-07 10:04 Arthur Zamarin
2022-05-07 9:58 Arthur Zamarin
2022-05-07 7:19 Sam James
2022-05-07 7:17 Sam James
2022-04-18 20:28 Sam James
2022-02-21 3:48 Sam James
2022-02-21 3:48 Sam James
2022-02-01 19:02 Michał Górny
2022-02-01 18:51 Michał Górny
2021-10-31 21:06 Mikle Kolyada
2021-10-28 14:57 Sam James
2021-08-18 0:35 Yixun Lan
2021-06-02 12:50 Sam James
2021-06-02 1:13 Sam James
2021-06-01 15:29 Sam James
2020-12-18 8:19 Mikle Kolyada
2020-10-10 7:58 Mikle Kolyada
2020-03-11 11:36 Mikle Kolyada
2020-03-11 11:36 Mikle Kolyada
2020-02-11 12:25 Michał Górny
2019-12-03 8:30 Mikle Kolyada
2019-11-30 15:40 Mikle Kolyada
2019-09-12 14:28 Michał Górny
2019-08-18 19:50 Mikle Kolyada
2019-02-23 20:57 Mikle Kolyada
2019-02-13 22:00 Mike Frysinger
2019-02-13 22:00 Mike Frysinger
2019-02-13 22:00 Mike Frysinger
2018-12-05 9:17 Mikle Kolyada
2018-12-05 9:09 Mikle Kolyada
2018-04-21 17:33 Mikle Kolyada
2018-03-25 13:29 Mikle Kolyada
2018-03-22 19:58 Mikle Kolyada
2017-12-15 7:33 Jeroen Roovers
2017-05-15 14:19 Manuel Rüger
2017-04-20 16:41 David Seifert
2017-01-15 11:20 Pacho Ramos
2016-12-20 15:30 Tobias Klausmann
2016-10-24 18:13 Markus Meier
2016-10-08 13:56 Pacho Ramos
2016-02-03 9:40 Patrice Clement
2016-02-02 22:24 Mike Frysinger
2016-01-04 10:17 Mike Frysinger
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=1513321170.3f427ebeb449b638a30deee93d87a27fa57b63aa.jer@gentoo \
--to=jer@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