From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/sysdig/
Date: Sun, 27 May 2018 09:03:59 +0000 (UTC) [thread overview]
Message-ID: <1527411830.bea34e168773d32e40c4c36cf0e2f1759ed218dd.mgorny@gentoo> (raw)
commit: bea34e168773d32e40c4c36cf0e2f1759ed218dd
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun May 27 08:48:13 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun May 27 09:03:50 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bea34e16
dev-util/sysdig: Drop old
dev-util/sysdig/Manifest | 1 -
dev-util/sysdig/sysdig-0.20.0.ebuild | 92 ------------------------------------
2 files changed, 93 deletions(-)
diff --git a/dev-util/sysdig/Manifest b/dev-util/sysdig/Manifest
index 4aefe654734..2811467779d 100644
--- a/dev-util/sysdig/Manifest
+++ b/dev-util/sysdig/Manifest
@@ -1,2 +1 @@
-DIST sysdig-0.20.0.tar.gz 750798 BLAKE2B 9e5c57abf81531f6643c661e539b06b33bda352eb3072e1ed686da3dc68550d90c94a4273554c2dd4752c73357f0bfe52bcbd10ad8551d8a2876552acf31292a SHA512 2549c8e2d0db0abd95e31272837fe5072c4c26926b2d17348bd8d73177bc024bab0a8503aa427f9134d8ca0a0bbc05fe97495933c3b8236db5fcb74df7c1efb2
DIST sysdig-0.21.0.tar.gz 756010 BLAKE2B 0dfcc3e7f5c830e8b250e4edd9d470764ea6be25804fefbc59b020f208edc313a51b3fb783e538d2acb520c56ad7c8555f224fb90999c87b89125394a90d54a1 SHA512 73c516c9fccb504d4ccd37384aee37ece542d29f82d696acf7c90df18b3a1538faf8d2b29065eae1f3dca7c04c6c2dbe93ed9369bc1340216482c4af2f61d23a
diff --git a/dev-util/sysdig/sysdig-0.20.0.ebuild b/dev-util/sysdig/sysdig-0.20.0.ebuild
deleted file mode 100644
index e366e662630..00000000000
--- a/dev-util/sysdig/sysdig-0.20.0.ebuild
+++ /dev/null
@@ -1,92 +0,0 @@
-# Copyright 1999-2018 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI="6"
-
-: ${CMAKE_MAKEFILE_GENERATOR:=ninja}
-MODULES_OPTIONAL_USE=modules
-inherit linux-mod bash-completion-r1 cmake-utils
-
-DESCRIPTION="A system exploration and troubleshooting tool"
-HOMEPAGE="https://www.sysdig.org/"
-SRC_URI="https://github.com/draios/sysdig/archive/${PV}.tar.gz -> ${P}.tar.gz"
-
-LICENSE="GPL-2"
-SLOT="0"
-KEYWORDS="~amd64 ~x86"
-IUSE="libressl +modules"
-
-RDEPEND="
- app-misc/jq:0=
- dev-lang/luajit:2=
- >=dev-libs/jsoncpp-0.6_pre:0=
- dev-libs/libb64:0=
- sys-libs/ncurses:0=
- sys-libs/zlib:0=
- libressl? ( dev-libs/libressl:0= )
- !libressl? ( dev-libs/openssl:0= )
- net-misc/curl:0="
-DEPEND="${RDEPEND}
- app-arch/xz-utils
- virtual/os-headers"
-
-# needed for the kernel module
-CONFIG_CHECK="HAVE_SYSCALL_TRACEPOINTS ~TRACEPOINTS"
-
-pkg_pretend() {
- linux-mod_pkg_setup
-}
-
-pkg_setup() {
- linux-mod_pkg_setup
-}
-
-src_prepare() {
- sed -i -e 's:-ggdb::' CMakeLists.txt || die
-
- cmake-utils_src_prepare
-}
-
-src_configure() {
- local mycmakeargs=(
- # we will use linux-mod for that
- -DBUILD_DRIVER=OFF
- # libscap examples are not installed or really useful
- -DBUILD_LIBSCAP_EXAMPLES=OFF
-
- # unbundle the deps
- -DUSE_BUNDLED_DEPS=OFF
- )
-
- cmake-utils_src_configure
-
- # setup linux-mod ugliness
- MODULE_NAMES="sysdig-probe(extra:${S}/driver:)"
- BUILD_PARAMS='KERNELDIR="${KERNEL_DIR}"'
- BUILD_TARGETS="all"
-
- if use modules; then
- cmake-utils_src_make configure_driver
-
- cp "${BUILD_DIR}"/driver/Makefile.dkms driver/Makefile || die
- fi
-}
-
-src_compile() {
- cmake-utils_src_compile
-
- linux-mod_src_compile
-}
-
-src_install() {
- cmake-utils_src_install
-
- linux-mod_src_install
-
- # remove sources
- rm -r "${ED%/}"/usr/src || die
-
- # move bashcomp to the proper location
- dobashcomp "${ED%/}"/usr/etc/bash_completion.d/sysdig || die
- rm -r "${ED%/}"/usr/etc || die
-}
next reply other threads:[~2018-05-27 9:04 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-27 9:03 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-21 19:57 [gentoo-commits] repo/gentoo:master commit in: dev-util/sysdig/ Sam James
2023-08-21 19:57 Sam James
2023-07-02 15:34 Sam James
2023-07-02 14:36 Sam James
2023-04-29 6:44 Sam James
2023-01-04 6:30 Arthur Zamarin
2023-01-03 18:28 Sam James
2022-08-23 5:34 Sam James
2022-03-09 15:11 Sam James
2022-03-09 15:11 Sam James
2021-12-15 16:12 Michał Górny
2021-05-02 17:56 Mikle Kolyada
2020-10-03 17:00 Michał Górny
2020-09-18 9:38 Michał Górny
2020-08-11 13:43 Michał Górny
2020-05-05 7:15 Michał Górny
2020-05-04 9:37 Michał Górny
2020-04-03 14:12 Michał Górny
2020-03-19 19:51 Michał Górny
2019-12-26 11:27 Michał Górny
2019-09-08 6:43 Michał Górny
2019-08-22 6:49 Michał Górny
2019-08-20 12:06 Michał Górny
2019-08-07 5:43 Michał Górny
2019-05-29 6:25 Michał Górny
2019-03-11 21:44 Michał Górny
2018-12-22 8:35 Michał Górny
2018-10-19 9:57 Michał Górny
2018-10-06 7:11 Michał Górny
2018-10-05 6:41 Michał Górny
2018-09-06 21:22 Michał Górny
2018-08-15 7:29 Michał Górny
2018-08-09 20:40 Michał Górny
2018-08-09 20:40 Michał Górny
2018-08-01 7:27 Michał Górny
2018-07-14 8:28 Michał Górny
2018-03-30 16:45 Michał Górny
2018-03-26 16:14 Michał Górny
2018-01-19 14:08 Michał Górny
2017-11-11 8:28 Michał Górny
2017-10-05 15:48 Michał Górny
2017-09-23 14:18 Michał Górny
2017-08-14 6:07 Michał Górny
2017-08-14 6:07 Michał Górny
2017-07-25 7:58 Michał Górny
2017-07-25 7:58 Michał Górny
2017-06-30 6:18 Michał Górny
2017-05-08 16:07 Michał Górny
2017-04-26 14:04 Michał Górny
2017-03-03 16:21 Thomas Deutschmann
2017-01-26 21:17 Michał Górny
2016-12-21 21:01 Michał Górny
2016-12-21 21:01 Michał Górny
2016-11-15 14:32 Michał Górny
2016-11-15 14:32 Michał Górny
2016-11-15 14:32 Michał Górny
2016-11-11 9:43 Michał Górny
2016-06-23 12:48 Michał Górny
2016-06-17 9:05 Michał Górny
2016-04-16 14:54 Michał Górny
2016-04-16 14:54 Michał Górny
2016-01-16 9:58 Michał Górny
2015-12-12 15:13 Michał Górny
2015-10-29 20:49 Michał Górny
2015-09-28 12:12 Justin Lecher
2015-09-28 11:10 Michał Górny
2015-09-28 11:10 Michał Górny
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=1527411830.bea34e168773d32e40c4c36cf0e2f1759ed218dd.mgorny@gentoo \
--to=mgorny@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