From: "Sebastien Fabbro" <bicatali@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/symengine/
Date: Wed, 26 Jul 2017 20:07:17 +0000 (UTC) [thread overview]
Message-ID: <1501099623.a7ed1c063ee79cf8c1a734905f575ecf92a7beea.bicatali@gentoo> (raw)
commit: a7ed1c063ee79cf8c1a734905f575ecf92a7beea
Author: Sébastien Fabbro <bicatali <AT> gentoo <DOT> org>
AuthorDate: Wed Jul 26 18:50:07 2017 +0000
Commit: Sebastien Fabbro <bicatali <AT> gentoo <DOT> org>
CommitDate: Wed Jul 26 20:07:03 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a7ed1c06
dev-python/symengine: avoid collision of README file with sci-libs/symengine
Package-Manager: Portage-2.3.6, Repoman-2.3.3
dev-python/symengine/symengine-0.3.0.ebuild | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/dev-python/symengine/symengine-0.3.0.ebuild b/dev-python/symengine/symengine-0.3.0.ebuild
index a9cd678259a..b972a264b22 100644
--- a/dev-python/symengine/symengine-0.3.0.ebuild
+++ b/dev-python/symengine/symengine-0.3.0.ebuild
@@ -31,3 +31,9 @@ python_test() {
cd "${BUILD_DIR}"
nosetests -v || die "tests failed with ${EPYTHON}"
}
+
+python_install_all() {
+ distutils-r1_python_prepare_all
+ rm "${ED}"/usr/share/doc/${PF}/README.md || die
+ newdoc README.md ${PN}.py.md
+}
next reply other threads:[~2017-07-26 20:07 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 20:07 Sebastien Fabbro [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-02 19:31 [gentoo-commits] repo/gentoo:master commit in: dev-python/symengine/ Michał Górny
2025-02-18 7:35 Michał Górny
2025-01-18 14:20 Jakov Smolić
2025-01-06 7:08 WANG Xuerui
2025-01-04 16:35 Sam James
2025-01-04 16:17 Sam James
2025-01-01 8:56 Joonas Niilola
2024-12-31 8:15 Sam James
2024-12-31 8:07 Michał Górny
2024-12-31 8:07 Michał Górny
2024-07-02 16:05 Michał Górny
2023-11-29 20:10 Arthur Zamarin
2023-11-29 19:38 Arthur Zamarin
2023-11-25 20:47 Sam James
2023-11-21 13:36 Michał Górny
2023-11-17 7:57 Michał Górny
2023-11-16 14:26 Michał Górny
2023-06-12 10:33 Sam James
2023-06-08 5:55 Michał Górny
2023-05-04 16:56 Michał Górny
2023-04-22 16:36 Michał Górny
2023-04-22 15:55 Arthur Zamarin
2023-04-22 15:55 Arthur Zamarin
2023-04-16 12:11 WANG Xuerui
2023-03-24 2:57 Sam James
2023-03-22 9:20 Sam James
2023-02-19 19:46 Michał Górny
2023-02-19 19:46 Michał Górny
2023-02-18 0:41 Sam James
2022-09-11 18:13 Sam James
2022-06-05 5:52 Michał Górny
2022-05-04 6:51 Agostino Sarubbo
2022-04-05 5:27 Agostino Sarubbo
2022-04-05 5:27 Agostino Sarubbo
2022-03-29 8:49 Yixun Lan
2022-03-28 6:51 Agostino Sarubbo
2022-03-27 6:27 Agostino Sarubbo
2022-03-15 22:17 Michał Górny
2022-02-22 5:40 Yixun Lan
2022-02-21 3:17 Sam James
2022-02-21 2:49 Sam James
2021-12-30 19:10 Arthur Zamarin
2021-12-30 19:04 Arthur Zamarin
2021-12-15 17:12 Andrew Ammerlaan
2021-12-14 19:52 Andrew Ammerlaan
2021-11-22 3:07 Yixun Lan
2021-05-04 13:59 Michał Górny
2021-05-04 7:03 Agostino Sarubbo
2021-04-30 15:23 Agostino Sarubbo
2021-03-27 7:49 Michał Górny
2021-03-14 8:12 Michał Górny
2020-10-27 19:58 Sam James
2020-10-27 5:11 Sam James
2020-09-18 15:53 Michał Górny
2020-08-31 15:35 Sam James
2020-08-31 14:15 Sam James
2020-08-31 13:49 Sam James
2020-08-30 23:18 Sam James
2020-08-02 19:05 Sam James
2020-08-02 6:46 Michał Górny
2020-08-02 6:46 Michał Górny
2020-03-22 12:12 Agostino Sarubbo
2020-03-19 21:56 David Seifert
2020-03-09 12:48 Agostino Sarubbo
2020-03-09 12:39 Agostino Sarubbo
2020-03-08 16:16 Andreas Sturmlechner
2020-03-08 16:02 Andreas Sturmlechner
2020-03-08 16:02 Andreas Sturmlechner
2020-03-08 16:02 Andreas Sturmlechner
2020-03-08 16:02 Andreas Sturmlechner
2020-01-16 6:05 Michał Górny
2019-12-28 11:57 罗百科
2017-07-26 20:07 Sebastien Fabbro
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=1501099623.a7ed1c063ee79cf8c1a734905f575ecf92a7beea.bicatali@gentoo \
--to=bicatali@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