public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-cpp/folly/
Date: Sun, 17 Apr 2022 16:44:03 +0000 (UTC)	[thread overview]
Message-ID: <1650213194.a1d4aa1e0578d83ac974c5989eb2c0ea902b4897.sam@gentoo> (raw)

commit:     a1d4aa1e0578d83ac974c5989eb2c0ea902b4897
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 17 16:33:14 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Apr 17 16:33:14 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a1d4aa1e

dev-cpp/folly: drop 2022.04.04.00

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-cpp/folly/Manifest                   |  1 -
 dev-cpp/folly/folly-2022.04.04.00.ebuild | 61 --------------------------------
 2 files changed, 62 deletions(-)

diff --git a/dev-cpp/folly/Manifest b/dev-cpp/folly/Manifest
index 98d01a86f77e..b5fa17da6fb9 100644
--- a/dev-cpp/folly/Manifest
+++ b/dev-cpp/folly/Manifest
@@ -1,3 +1,2 @@
 DIST folly-2022.03.28.00.tar.gz 3616507 BLAKE2B da003701abe599f20ac87a2785fe9a4cd4a8896d182737eb1eac6384f3d75a792225b426febea7cc4ea99aac1a1f31eb7330e0a297f43ae7d5aafccd93784560 SHA512 6eee07b3e82247c3c8672442503e9a69a1c4607604269fc0760e11a2d0e5595029e6995fbe7c970d2052a7f228f6b92112630e6d5c624369fc52e5ad1823ef74
-DIST folly-2022.04.04.00.tar.gz 3629241 BLAKE2B 6e606c7412a8c2dcf731bf1373d3ed33680b07641109fd5da066bd648961d9608d82496322496bf6334a8576ae2394a36603ba8098e972c9b949a989f04baa4f SHA512 923cab43820b75ef7f614a3e62d278ecb3a64beeabefee64d6fb113fbbfd368b69a2a90015706ba58e68967eb9bbf97052678edd1f2d6d4d466792f08e547488
 DIST folly-2022.04.11.00.tar.gz 3632587 BLAKE2B 13820f6dc600727fa97603181be97a568cc8b3c713659717592853827dac050d5f1f6d98178e3054871233b48ac18f713589bf43b36ea29445cad557ce13bacf SHA512 7aa0be95d6f8b21aaa88558cf5921c526ab5a8c8121b858eb6e7ea19946d7a82dff06d90b7a365cef5c56a43d8d57af8d01b8b11b27262fbed9ee8c9e701b5ac

diff --git a/dev-cpp/folly/folly-2022.04.04.00.ebuild b/dev-cpp/folly/folly-2022.04.04.00.ebuild
deleted file mode 100644
index b644181fecc6..000000000000
--- a/dev-cpp/folly/folly-2022.04.04.00.ebuild
+++ /dev/null
@@ -1,61 +0,0 @@
-# Copyright 1999-2022 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=8
-
-inherit cmake toolchain-funcs
-
-DESCRIPTION="An open-source C++ library developed and used at Facebook"
-HOMEPAGE="https://github.com/facebook/folly"
-SRC_URI="https://github.com/facebook/folly/archive/v${PV}.tar.gz -> ${P}.tar.gz"
-
-LICENSE="Apache-2.0"
-SLOT="0/${PV}"
-KEYWORDS="~amd64"
-IUSE="llvm-libunwind test"
-RESTRICT="!test? ( test )"
-
-RDEPEND="app-arch/bzip2
-	app-arch/lz4:=
-	app-arch/snappy:=
-	app-arch/xz-utils
-	app-arch/zstd:=
-	dev-cpp/gflags:=
-	dev-cpp/glog[gflags]
-	dev-libs/boost:=[context,threads(+)]
-	dev-libs/double-conversion:=
-	dev-libs/libaio
-	dev-libs/libevent:=
-	dev-libs/libfmt:=
-	dev-libs/libsodium:=
-	dev-libs/openssl:=
-	sys-libs/liburing:=
-	sys-libs/zlib
-	llvm-libunwind? ( sys-libs/llvm-libunwind:= )
-	!llvm-libunwind? ( sys-libs/libunwind:= )"
-# libiberty is linked statically
-DEPEND="${RDEPEND}
-	sys-libs/binutils-libs"
-BDEPEND="test? ( sys-devel/clang )"
-
-pkg_setup() {
-	if use test && [[ ${BUILD_TYPE} != "binary" ]] && ! tc-is-clang ; then
-		ewarn "Forcing build with Clang due to GCC bug (because tests are enabled)"
-		ewarn "(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104008)"
-
-		export CC=${CHOST}-clang
-		export CXX=${CHOST}-clang++
-	fi
-}
-
-src_configure() {
-	# TODO: liburing could in theory be optional but fails to link
-
-	local mycmakeargs=(
-		-DLIB_INSTALL_DIR="$(get_libdir)"
-
-		-DBUILD_TESTS=$(usex test)
-	)
-
-	cmake_src_configure
-}


             reply	other threads:[~2022-04-17 16:44 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-17 16:44 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-05 10:06 [gentoo-commits] repo/gentoo:master commit in: dev-cpp/folly/ Arthur Zamarin
2024-12-01 11:47 Sam James
2024-12-01 11:47 Sam James
2024-11-23 20:16 Sam James
2024-11-23 14:01 Sam James
2024-11-23 14:01 Sam James
2024-11-15  9:51 Petr Vaněk
2024-11-11 22:25 Sam James
2023-06-24  8:29 Arthur Zamarin
2023-06-24  6:32 Sam James
2023-06-24  5:39 Sam James
2023-05-04  9:03 Sam James
2023-05-01  1:43 Sam James
2023-04-14  3:39 Sam James
2023-02-17  8:59 Sam James
2023-02-16  3:29 Sam James
2023-02-06 21:25 Sam James
2023-01-23 20:25 Sam James
2022-12-21 22:54 Sam James
2022-12-16 20:48 Arthur Zamarin
2022-09-18  0:35 Sam James
2022-09-18  0:35 Sam James
2022-09-06  4:18 Sam James
2022-08-29 20:13 Sam James
2022-08-23  3:51 Sam James
2022-08-23  3:30 Sam James
2022-08-15 18:19 Sam James
2022-08-13 15:09 Sam James
2022-08-13 15:09 Sam James
2022-07-09  4:25 Sam James
2022-07-08  0:57 Sam James
2022-05-16 12:51 Agostino Sarubbo
2022-04-16  3:07 Sam James
2022-04-05  3:08 Sam James
2022-04-05  3:08 Sam James
2022-04-01  3:53 Sam James
2022-04-01  3:53 Sam James
2022-03-22  1:48 Sam James
2022-03-18  6:16 Sam James
2022-03-09 15:34 Sam James
2022-03-07  7:31 Sam James
2022-03-07  3:24 Sam James

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=1650213194.a1d4aa1e0578d83ac974c5989eb2c0ea902b4897.sam@gentoo \
    --to=sam@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