From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: sci-biology/bamtools/
Date: Mon, 6 Jan 2014 19:27:07 +0000 (UTC) [thread overview]
Message-ID: <1389034882.ad690538196efa3671c800664cab5b808cf9690c.jlec@gentoo> (raw)
commit: ad690538196efa3671c800664cab5b808cf9690c
Author: Justin Lecher <jlec <AT> gentoo <DOT> org>
AuthorDate: Mon Jan 6 19:01:22 2014 +0000
Commit: Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Mon Jan 6 19:01:22 2014 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/sci.git;a=commit;h=ad690538
sci-biology/bamtools: Switch from git-2 to git-r3
Package-Manager: portage-2.2.8
---
sci-biology/bamtools/ChangeLog | 6 +++++-
sci-biology/bamtools/bamtools-9999.ebuild | 10 ++++------
sci-biology/bamtools/metadata.xml | 12 ++++++------
3 files changed, 15 insertions(+), 13 deletions(-)
diff --git a/sci-biology/bamtools/ChangeLog b/sci-biology/bamtools/ChangeLog
index 6ff7212..8afcd01 100644
--- a/sci-biology/bamtools/ChangeLog
+++ b/sci-biology/bamtools/ChangeLog
@@ -1,7 +1,11 @@
# ChangeLog for sci-biology/bamtools
-# Copyright 1999-2012 Gentoo Foundation; Distributed under the GPL v2
+# Copyright 1999-2014 Gentoo Foundation; Distributed under the GPL v2
# $Header: $
+ 06 Jan 2014; Justin Lecher <jlec@gentoo.org> bamtools-9999.ebuild,
+ metadata.xml:
+ Switch from git-2 to git-r3
+
09 Nov 2012; Justin Lecher <jlec@gentoo.org> -bamtools-1.0.2.ebuild,
bamtools-9999.ebuild:
Drop tree version, merge changes into live version
diff --git a/sci-biology/bamtools/bamtools-9999.ebuild b/sci-biology/bamtools/bamtools-9999.ebuild
index b92abe0..575b69a 100644
--- a/sci-biology/bamtools/bamtools-9999.ebuild
+++ b/sci-biology/bamtools/bamtools-9999.ebuild
@@ -1,13 +1,14 @@
-# Copyright 1999-2012 Gentoo Foundation
+# Copyright 1999-2014 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $
-EAPI=4
+EAPI=5
-inherit cmake-utils git-2
+inherit cmake-utils git-r3
DESCRIPTION="A programmer's API and an end-user's toolkit for handling BAM files"
HOMEPAGE="https://github.com/pezmaster31/bamtools"
+SRC_URI=""
EGIT_REPO_URI="https://github.com/pezmaster31/bamtools.git"
LICENSE="MIT"
@@ -15,9 +16,6 @@ SLOT="0"
KEYWORDS=""
IUSE=""
-DEPEND="sys-libs/zlib"
-RDEPEND="${DEPEND}"
-
S="${WORKDIR}"/src
src_install() {
diff --git a/sci-biology/bamtools/metadata.xml b/sci-biology/bamtools/metadata.xml
index e10e621..e304b12 100644
--- a/sci-biology/bamtools/metadata.xml
+++ b/sci-biology/bamtools/metadata.xml
@@ -1,10 +1,10 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <herd>sci-biology</herd>
- <maintainer>
- <email>mmokrejs@fold.natur.cuni.cz</email>
- <name>Martin Mokrejs</name>
- </maintainer>
- <longdescription>BAM (Binary Alignment/Map) format is useful for storing large DNA sequence alignments. It is closely related to the text-based SAM format, but optimized for random-access. BamTools provides a fast, flexible C++ API for reading and writing BAM files.</longdescription>
+ <herd>sci-biology</herd>
+ <maintainer>
+ <email>mmokrejs@fold.natur.cuni.cz</email>
+ <name>Martin Mokrejs</name>
+ </maintainer>
+ <longdescription>BAM (Binary Alignment/Map) format is useful for storing large DNA sequence alignments. It is closely related to the text-based SAM format, but optimized for random-access. BamTools provides a fast, flexible C++ API for reading and writing BAM files.</longdescription>
</pkgmetadata>
next reply other threads:[~2014-01-06 19:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 19:27 Justin Lecher [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-29 11:59 [gentoo-commits] proj/sci:master commit in: sci-biology/bamtools/ Justin Lecher
2016-12-19 20:06 Martin Mokrejs
2016-04-10 11:31 Martin Mokrejs
2012-11-09 14:35 Justin Lecher
2011-09-10 14:10 Martin Mokrejs
2011-09-08 20:23 Martin Mokrejs
2011-06-25 17:21 Justin Lecher
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=1389034882.ad690538196efa3671c800664cab5b808cf9690c.jlec@gentoo \
--to=jlec@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