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: sys-apps/keyutils/
Date: Wed,  7 Feb 2024 19:20:29 +0000 (UTC)	[thread overview]
Message-ID: <1707333600.624363fd24ce66be030fc0270524a63a67458e02.sam@gentoo> (raw)

commit:     624363fd24ce66be030fc0270524a63a67458e02
Author:     Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Wed Feb  7 06:14:58 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Feb  7 19:20:00 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=624363fd

sys-apps/keyutils: remove usr-ldscript support

Per news item 2024-01-05-usr-initramfs, we no longer support this use
case. It is fragile and hacky and leads to bizarre forms of load errors.

The functionality is, despite being called "split-usr", not really about
split-usr at all.

Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>

 sys-apps/keyutils/keyutils-1.6.3-r1.ebuild | 115 +++++++++++++++++++++++++++++
 1 file changed, 115 insertions(+)

diff --git a/sys-apps/keyutils/keyutils-1.6.3-r1.ebuild b/sys-apps/keyutils/keyutils-1.6.3-r1.ebuild
new file mode 100644
index 000000000000..37ead31590a3
--- /dev/null
+++ b/sys-apps/keyutils/keyutils-1.6.3-r1.ebuild
@@ -0,0 +1,115 @@
+# Copyright 1999-2024 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+inherit toolchain-funcs linux-info multilib-minimal
+
+DESCRIPTION="Linux Key Management Utilities"
+HOMEPAGE="https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/keyutils.git"
+SRC_URI="https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/keyutils.git/snapshot/${P}.tar.gz"
+
+LICENSE="GPL-2 LGPL-2.1"
+SLOT="0/1.9"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux"
+IUSE="static static-libs test"
+RESTRICT="!test? ( test )"
+
+RDEPEND=""
+DEPEND="!prefix? ( >=sys-kernel/linux-headers-2.6.11 )"
+
+PATCHES=(
+	"${FILESDIR}"/${PN}-1.6-makefile-fixup.patch
+	"${FILESDIR}"/${PN}-1.5.10-disable-tests.patch #519062 #522050
+	"${FILESDIR}"/${PN}-1.5.9-header-extern-c.patch
+	"${FILESDIR}"/${PN}-1.6.3-fix-rpmspec-check.patch
+)
+
+pkg_setup() {
+	# To prevent a failure in test phase and false positive bug reports
+	# we are enforcing the following options because testsuite expects
+	# that these options are available. I.e. testsuite only decides based
+	# on kernel version which tests will be called, no feature checking.
+	if use test ; then
+		CONFIG_CHECK="KEYS"
+		ERROR_KEYS="You must have CONFIG_KEYS to run the package testsuite!"
+
+		if kernel_is -ge 2 6 10 && kernel_is -lt 4 0 0 ; then
+			CONFIG_CHECK="${CONFIG_CHECK} KEYS_DEBUG_PROC_KEYS"
+			ERROR_KEYS_DEBUG_PROC_KEYS="You must have CONFIG_KEYS_DEBUG_PROC_KEYS to run the package testsuite!"
+		fi
+
+		if kernel_is -ge 4 7 ; then
+			CONFIG_CHECK="${CONFIG_CHECK} KEY_DH_OPERATIONS"
+			ERROR_KEY_DH_OPERATIONS="You must have CONFIG_KEY_DH_OPERATIONS to run the package testsuite!"
+		fi
+	else
+		CONFIG_CHECK="~KEYS"
+		ERROR_KEYS="You will be unable to use this package on this system because CONFIG_KEYS is not set!"
+
+		if kernel_is -ge 4 7 ; then
+			CONFIG_CHECK="${CONFIG_CHECK} ~KEY_DH_OPERATIONS"
+			ERROR_KEY_DH_OPERATIONS="You will be unable to use Diffie-Hellman on this system because CONFIG_KEY_DH_OPERATIONS is not set!"
+		fi
+	fi
+
+	linux-info_pkg_setup
+}
+
+src_prepare() {
+	default
+
+	# The lsb check is useless, so avoid spurious command not found messages.
+	sed -i -e 's,lsb_release,:,' tests/prepare.inc.sh || die
+	# Some tests call the kernel which calls userspace, but that will
+	# run the install keyutils rather than the locally compiled one,
+	# so disable round trip tests.
+	rm -rf tests/keyctl/requesting/{bad-args,piped,valid}
+
+	multilib_copy_sources
+}
+
+multilib_src_compile() {
+	tc-export AR CC CXX
+	sed -i \
+		-e "1iRPATH = $(usex static -static '')" \
+		-e '/^C.*FLAGS/s|:=|+=|' \
+		-e 's:-Werror::' \
+		-e '/^BUILDFOR/s:=.*:=:' \
+		-e "/^LIBDIR/s:=.*:= /usr/$(get_libdir):" \
+		-e '/^USRLIBDIR/s:=.*:=$(LIBDIR):' \
+		-e "s: /: ${EPREFIX}/:g" \
+		-e '/^NO_ARLIB/d' \
+		Makefile || die
+
+	# We need the static lib in order to statically link programs.
+	if use static ; then
+		export NO_ARLIB=0
+		# Hack the progs to depend on the static lib instead.
+		sed -i \
+			-e '/^.*:.*[$](DEVELLIB)$/s:$(DEVELLIB):$(ARLIB) $(SONAME):' \
+			Makefile || die
+	else
+		export NO_ARLIB=$(usex static-libs 0 1)
+	fi
+	emake
+}
+
+multilib_src_test() {
+	# Execute the locally compiled code rather than the
+	# older versions already installed in the system.
+	LD_LIBRARY_PATH=${BUILD_DIR} \
+	PATH="${BUILD_DIR}:${PATH}" \
+	emake test
+}
+
+multilib_src_install() {
+	# Possibly undo the setting for USE=static (see src_compile).
+	export NO_ARLIB=$(usex static-libs 0 1)
+
+	default
+}
+
+multilib_src_install_all() {
+	dodoc README
+}


             reply	other threads:[~2024-02-07 19:20 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 19:20 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-15  0:12 [gentoo-commits] repo/gentoo:master commit in: sys-apps/keyutils/ Mike Gilbert
2024-03-03  4:00 Sam James
2024-03-02 12:12 Arthur Zamarin
2024-03-02 12:12 Arthur Zamarin
2024-03-02 12:12 Arthur Zamarin
2024-03-02 12:12 Arthur Zamarin
2024-03-02 12:12 Arthur Zamarin
2024-03-02 12:12 Arthur Zamarin
2024-01-05 14:02 Sam James
2024-01-05 14:02 Sam James
2023-10-10  4:34 Sam James
2023-04-06  5:18 Sam James
2023-04-06  4:50 Sam James
2022-12-26  8:35 Sam James
2022-11-22  8:04 Arthur Zamarin
2022-10-29 14:45 Sam James
2022-05-11  0:49 Sam James
2022-05-11  0:49 Sam James
2022-05-10 14:34 Agostino Sarubbo
2022-05-10 13:47 Agostino Sarubbo
2022-05-10 13:47 Agostino Sarubbo
2022-04-27 18:06 Arthur Zamarin
2022-01-14 14:42 Arthur Zamarin
2022-01-13  2:56 Georgy Yakovlev
2021-05-13 16:15 Sam James
2021-05-13 13:55 David Seifert
2020-07-08 11:34 Thomas Deutschmann
2020-07-07 17:08 Thomas Deutschmann
2020-01-06 11:52 Mike Frysinger
2019-11-02  0:23 Sergei Trofimovich
2019-09-22  9:32 Agostino Sarubbo
2019-09-21  5:20 Matt Turner
2019-09-16  7:55 Agostino Sarubbo
2019-09-13 18:01 Mikle Kolyada
2019-09-11  8:43 Agostino Sarubbo
2019-09-11  8:41 Agostino Sarubbo
2019-09-11  8:28 Agostino Sarubbo
2019-09-11  8:20 Agostino Sarubbo
2019-09-09 17:20 Aaron Bauman
2019-05-05 12:06 Mikle Kolyada
2018-11-16 12:53 Lars Wendler
2018-09-01  1:32 Thomas Deutschmann
2018-08-31 14:55 Thomas Deutschmann
2018-08-31 14:55 Thomas Deutschmann
2018-08-31 14:55 Thomas Deutschmann
2018-08-31 14:55 Thomas Deutschmann
2018-08-31  2:54 Thomas Deutschmann
2018-08-02 15:50 Lars Wendler
2018-03-11  6:24 Matt Turner
2018-03-11  1:12 Matt Turner
2018-02-18 12:28 Tobias Klausmann
2018-01-24 21:25 Sergei Trofimovich
2018-01-12  4:10 Mike Frysinger
2018-01-09  8:09 Sergei Trofimovich
2018-01-04 15:42 Lars Wendler
2018-01-04 15:25 Lars Wendler
2017-05-24 16:30 Lars Wendler
2017-03-14 21:03 Mike Frysinger
2016-04-18 19:10 Mike Frysinger
2016-03-30 23:48 Mike Frysinger
2016-03-30 23:48 Mike Frysinger

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=1707333600.624363fd24ce66be030fc0270524a63a67458e02.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