From: "David Seifert" <soap@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-cpp/sparsehash/
Date: Wed, 17 Feb 2021 09:37:14 +0000 (UTC) [thread overview]
Message-ID: <1613554557.997a3e4fbe7102d1d4d0a3da0759a9d6bb7c9c43.soap@gentoo> (raw)
commit: 997a3e4fbe7102d1d4d0a3da0759a9d6bb7c9c43
Author: Jakov Smolic <jakov.smolic <AT> sartura <DOT> hr>
AuthorDate: Wed Feb 17 09:35:57 2021 +0000
Commit: David Seifert <soap <AT> gentoo <DOT> org>
CommitDate: Wed Feb 17 09:35:57 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=997a3e4f
dev-cpp/sparsehash: Remove old
Signed-off-by: Jakov Smolic <jakov.smolic <AT> sartura.hr>
Signed-off-by: David Seifert <soap <AT> gentoo.org>
dev-cpp/sparsehash/Manifest | 1 -
dev-cpp/sparsehash/sparsehash-2.0.3-r1.ebuild | 24 ------------------------
2 files changed, 25 deletions(-)
diff --git a/dev-cpp/sparsehash/Manifest b/dev-cpp/sparsehash/Manifest
index d0657506022..599137f008d 100644
--- a/dev-cpp/sparsehash/Manifest
+++ b/dev-cpp/sparsehash/Manifest
@@ -1,2 +1 @@
-DIST sparsehash-2.0.3.tar.gz 322046 BLAKE2B 3749875bfbfa0ec9b92cfe68496a318208539745ca1b76910193879cb9ac790952b390cfbd941ff6e9714bd61546844e8f2d958d9b24845efeb54743facac136 SHA512 bb00d0acb8eba65f7da8015ea4f6bebf8bba36ed6777881960ee215f22b7be17b069c59838d210551ce67a34baccfc7b2fed603677ec53c0c32714d8e76f5d6c
DIST sparsehash-2.0.4.tar.gz 323154 BLAKE2B 8e0da89a6ae684271293f048092d6c79d14818f7ab9d4fa449414b3354f9e7769d9b0cc724227c47a1be7c7357cdac5cf6f3873047a08c8f085cc457858a8826 SHA512 40c007bc5814dd5f2bdacd5ec884bc5424f7126f182d4c7b34371f88b674456fc193b947fdd283dbd0c7eb044d8f06baf8caec6c93e73b1b587282b9026ea877
diff --git a/dev-cpp/sparsehash/sparsehash-2.0.3-r1.ebuild b/dev-cpp/sparsehash/sparsehash-2.0.3-r1.ebuild
deleted file mode 100644
index b043e1800ff..00000000000
--- a/dev-cpp/sparsehash/sparsehash-2.0.3-r1.ebuild
+++ /dev/null
@@ -1,24 +0,0 @@
-# Copyright 1999-2017 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=6
-
-inherit autotools
-
-DESCRIPTION="An extremely memory-efficient hash_map implementation"
-HOMEPAGE="https://github.com/sparsehash/sparsehash"
-SRC_URI="https://github.com/${PN}/${PN}/archive/${P}.tar.gz"
-
-LICENSE="BSD"
-SLOT="0"
-KEYWORDS="amd64 x86 ~amd64-linux ~x86-linux"
-IUSE=""
-
-S=${WORKDIR}/${PN}-${P}
-
-PATCHES=( "${FILESDIR}"/${PN}-2.0.3-fix-buildsystem.patch )
-
-src_prepare() {
- default
- eautoreconf
-}
next reply other threads:[~2021-02-17 9:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 9:37 David Seifert [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-08 12:50 [gentoo-commits] repo/gentoo:master commit in: dev-cpp/sparsehash/ Jakov Smolić
2024-10-06 10:55 Sam James
2024-10-06 10:49 Sam James
2024-08-30 15:31 Jakov Smolić
2021-02-16 8:25 Sergei Trofimovich
2020-12-16 23:10 Sam James
2020-12-13 21:45 Thomas Deutschmann
2020-12-07 18:48 Sam James
2020-11-12 7:51 Joonas Niilola
2020-11-12 7:51 Joonas Niilola
2020-11-12 7:51 Joonas Niilola
2017-03-01 20:35 David Seifert
2017-01-23 15:46 Agostino Sarubbo
2017-01-23 13:51 Agostino Sarubbo
2016-01-14 0:24 Tim Harder
2015-09-01 18:57 Tobias Klausmann
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=1613554557.997a3e4fbe7102d1d4d0a3da0759a9d6bb7c9c43.soap@gentoo \
--to=soap@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