From: "Martin Mokrejs" <mmokrejs@fold.natur.cuni.cz>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: sci-biology/exonerate-gff3/
Date: Thu, 30 Jun 2016 17:20:04 +0000 (UTC) [thread overview]
Message-ID: <1467307191.759fd10bc6e0ea8406ac7effe97fb17d740cf2fe.mmokrejs@gentoo> (raw)
commit: 759fd10bc6e0ea8406ac7effe97fb17d740cf2fe
Author: Martin Mokrejš <mmokrejs <AT> fold <DOT> natur <DOT> cuni <DOT> cz>
AuthorDate: Thu Jun 30 17:19:51 2016 +0000
Commit: Martin Mokrejs <mmokrejs <AT> fold <DOT> natur <DOT> cuni <DOT> cz>
CommitDate: Thu Jun 30 17:19:51 2016 +0000
URL: https://gitweb.gentoo.org/proj/sci.git/commit/?id=759fd10b
sci-biology/exonerate-gff3: undo commit 5f9c9c1d2a68a9a5f29d3c060ff807becd70fe5f
It is unclear to me what Justin did but seems it was by mistake. This changes
now keeps this ebuild in sync with sci-biology/exonerate::gentoo ebuild and
patches configure.in file again. This at least works for me.
Package-Manager: portage-2.2.28
sci-biology/exonerate-gff3/exonerate-gff3-9999.ebuild | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/sci-biology/exonerate-gff3/exonerate-gff3-9999.ebuild b/sci-biology/exonerate-gff3/exonerate-gff3-9999.ebuild
index fda6c78..48a49b6 100644
--- a/sci-biology/exonerate-gff3/exonerate-gff3-9999.ebuild
+++ b/sci-biology/exonerate-gff3/exonerate-gff3-9999.ebuild
@@ -35,7 +35,8 @@ src_prepare() {
sed \
-e 's: -O3 -finline-functions::g' \
-i configure.in || die
- mv configure.in configure.ac
+ # we patch the configure.in file like sci-biology/exonerate:gentoo does, though it is ugly hack
+ # mv configure.in configure.ac
autotools-utils_src_prepare
}
next reply other threads:[~2016-06-30 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 17:20 Martin Mokrejs [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-24 14:25 [gentoo-commits] proj/sci:master commit in: sci-biology/exonerate-gff3/ Andrew Ammerlaan
2021-01-19 16:26 Andrew Ammerlaan
2016-06-29 15:35 Martin Mokrejs
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=1467307191.759fd10bc6e0ea8406ac7effe97fb17d740cf2fe.mmokrejs@gentoo \
--to=mmokrejs@fold.natur.cuni.cz \
--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