From: "Martin Mokrejs" <mmokrejs@fold.natur.cuni.cz>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: sci-biology/jellyfish/
Date: Tue, 21 Nov 2017 16:09:13 +0000 (UTC) [thread overview]
Message-ID: <1511280534.03271b4b44f838754e7af1b70c62366c42f4d4d2.mmokrejs@gentoo> (raw)
commit: 03271b4b44f838754e7af1b70c62366c42f4d4d2
Author: Martin Mokrejš <mmokrejs <AT> fold <DOT> natur <DOT> cuni <DOT> cz>
AuthorDate: Tue Nov 21 16:08:54 2017 +0000
Commit: Martin Mokrejs <mmokrejs <AT> fold <DOT> natur <DOT> cuni <DOT> cz>
CommitDate: Tue Nov 21 16:08:54 2017 +0000
URL: https://gitweb.gentoo.org/proj/sci.git/commit/?id=03271b4b
sci-biology/jellyfish: rename jellyfish to jellyfish1
This will facilitate simultaneous installs of jeelyfish2
and jellyfish, so that sci-biology/SEECER and sci-biology/quorum
could be installed at the same time (both calling "jellyfish"
but quorum needs version 2 and SEECER version 1.
See list of files at https://packages.debian.org/unstable/jellyfish1
Package-Manager: Portage-2.3.14, Repoman-2.3.6
.../jellyfish/{jellyfish-1.1.11.ebuild => jellyfish-1.1.11-r1.ebuild} | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/sci-biology/jellyfish/jellyfish-1.1.11.ebuild b/sci-biology/jellyfish/jellyfish-1.1.11-r1.ebuild
similarity index 85%
rename from sci-biology/jellyfish/jellyfish-1.1.11.ebuild
rename to sci-biology/jellyfish/jellyfish-1.1.11-r1.ebuild
index 9134a98d4..923784ada 100644
--- a/sci-biology/jellyfish/jellyfish-1.1.11.ebuild
+++ b/sci-biology/jellyfish/jellyfish-1.1.11-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2016 Gentoo Foundation
+# Copyright 1999-2017 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -34,6 +34,8 @@ src_prepare(){
}
src_install(){
+ # install the binary under jellyfish1 name like Debian/Ubuntu to avoid name clash with jellyfish2 and allow simultaneous installs
+ mv bin/jellyfish bin/jellyfish1 || die
default
sed -e "s#jellyfish-${PV}#jellyfish#" -i "${ED}/usr/$(get_libdir)"/pkgconfig/jellyfish-1.1.pc || die
mkdir -p "${ED}/usr/include/${PN}" || die
next reply other threads:[~2017-11-21 16:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 16:09 Martin Mokrejs [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-20 4:11 [gentoo-commits] proj/sci:master commit in: sci-biology/jellyfish/ Horea Christian
2023-04-20 4:11 Horea Christian
2023-04-20 4:11 Horea Christian
2022-01-14 10:10 Andrew Ammerlaan
2021-06-06 0:38 Jakov Smolić
2021-03-06 11:34 Andrew Ammerlaan
2021-03-06 11:34 Andrew Ammerlaan
2019-07-18 16:10 Martin Mokrejs
2018-09-11 11:21 Martin Mokrejs
2018-05-01 22:13 Martin Mokrejs
2018-04-23 19:13 Martin Mokrejs
2018-04-21 19:43 Martin Mokrejs
2017-05-15 15:56 Martin Mokrejs
2017-05-15 14:21 Martin Mokrejs
2017-05-15 14:17 Martin Mokrejs
2016-12-09 16:24 Martin Mokrejs
2016-03-06 19:44 Justin Lecher
2015-11-13 19:11 Martin Mokrejs
2015-05-04 14:45 Justin Lecher
2015-04-30 22:02 Martin Mokrejs
2015-04-30 21:29 Martin Mokrejs
2015-04-30 21:28 Martin Mokrejs
2015-04-30 20:32 Martin Mokrejs
2015-04-30 10:11 Martin Mokrejs
2015-03-31 22:34 Martin Mokrejs
2015-03-31 19:50 Martin Mokrejs
2015-01-07 21:43 Martin Mokrejs
2014-07-02 23:15 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=1511280534.03271b4b44f838754e7af1b70c62366c42f4d4d2.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