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-fs/loop-aes/
Date: Wed, 20 Oct 2021 01:51:31 +0000 (UTC)	[thread overview]
Message-ID: <1634694497.8994a9ab9245a3894d50af4360a2b1fc93510169.sam@gentoo> (raw)

commit:     8994a9ab9245a3894d50af4360a2b1fc93510169
Author:     Hank Leininger <hlein <AT> korelogic <DOT> com>
AuthorDate: Mon Oct 11 16:42:25 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Oct 20 01:48:17 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8994a9ab

sys-fs/loop-aes: drop old

Signed-off-by: Hank Leininger <hlein <AT> korelogic.com>
Package-Manager: Portage-3.0.28, Repoman-3.0.3
Closes: https://github.com/gentoo/gentoo/pull/22557
Signed-off-by: Sam James <sam <AT> gentoo.org>

 sys-fs/loop-aes/Manifest             |  1 -
 sys-fs/loop-aes/loop-aes-3.7t.ebuild | 71 ------------------------------------
 2 files changed, 72 deletions(-)

diff --git a/sys-fs/loop-aes/Manifest b/sys-fs/loop-aes/Manifest
index 961706a8edd..25aeb63a47a 100644
--- a/sys-fs/loop-aes/Manifest
+++ b/sys-fs/loop-aes/Manifest
@@ -1,2 +1 @@
-DIST loop-AES-v3.7t.tar.bz2 377808 BLAKE2B 77a6baa31be9efc84504e6eaccca87193180b26ec6f6dc824480453e78905f8763c08fd72a63c18950796ad0b70ad8be2ed26e107cded6dcaddd96433dfa7f56 SHA512 cb0dcbfa7639f8d2c1990465a44cbcd6d4bf065b1df9178f4dd524a8b8ddd05ebb860e6a9d9425b4a22b9c74342bf3ff232ff777be9b5458bdabe54f4097ecef
 DIST loop-AES-v3.7v.tar.bz2 378465 BLAKE2B 01d9c3719242846696c1e199a02a42254c06472abce6cee7ccc3882e456921176f7469e9c61331193dd86ee2fcf0d24972f9012026eadad150a8e6116dd4e275 SHA512 62c0bafd97bc07d78d128ba3bbcf471bf16bd979264ad9180132b83f01a1e8d4f6d9aa874c602a00bc85360abfefe16f72b28b2c73cc2ad863ea2d36eb7bc478

diff --git a/sys-fs/loop-aes/loop-aes-3.7t.ebuild b/sys-fs/loop-aes/loop-aes-3.7t.ebuild
deleted file mode 100644
index 116820a36e6..00000000000
--- a/sys-fs/loop-aes/loop-aes-3.7t.ebuild
+++ /dev/null
@@ -1,71 +0,0 @@
-# Copyright 1999-2021 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=7
-
-inherit linux-mod
-
-MY_P="${PN/aes/AES}-v${PV}"
-
-DESCRIPTION="Linux kernel module to encrypt disk partitions with AES cipher"
-HOMEPAGE="http://loop-aes.sourceforge.net/loop-AES.README"
-SRC_URI="http://loop-aes.sourceforge.net/loop-AES/${MY_P}.tar.bz2"
-
-LICENSE="GPL-2"
-SLOT="0"
-KEYWORDS="~amd64 ~arm ~hppa ~ppc ~sparc ~x86"
-IUSE="cpu_flags_x86_aes extra-ciphers keyscrub cpu_flags_x86_padlock"
-
-DEPEND="app-crypt/loop-aes-losetup"
-
-S="${WORKDIR}/${MY_P}"
-
-pkg_setup() {
-	linux-mod_pkg_setup
-
-	CONFIG_CHECK="!BLK_DEV_LOOP"
-	MODULE_NAMES="loop(block::tmp-d-kbuild)"
-	BUILD_TARGETS="all"
-
-	BUILD_PARAMS=" \
-		V=1 \
-		LINUX_SOURCE=\"${KERNEL_DIR}\" \
-		KBUILD_OUTPUT=\"${KBUILD_OUTPUT}\" \
-		USE_KBUILD=y MODINST=n RUNDM=n"
-	use cpu_flags_x86_aes && BUILD_PARAMS+=" INTELAES=y"
-	use keyscrub && BUILD_PARAMS+=" KEYSCRUB=y"
-	use cpu_flags_x86_padlock && BUILD_PARAMS+=" PADLOCK=y"
-
-	if use extra-ciphers; then
-		MODULE_NAMES="${MODULE_NAMES}
-			loop_blowfish(block::tmp-d-kbuild)
-			loop_serpent(block::tmp-d-kbuild)
-			loop_twofish(block::tmp-d-kbuild)"
-		BUILD_PARAMS+=" EXTRA_CIPHERS=y"
-	fi
-}
-
-src_install() {
-	linux-mod_src_install
-
-	dodoc README
-	dobin loop-aes-keygen
-	doman loop-aes-keygen.1
-
-	into /
-	dosbin build-initrd.sh
-}
-
-pkg_postinst() {
-	linux-mod_pkg_postinst
-
-	einfo
-	einfo "For more instructions take a look at examples in README at:"
-	einfo "'${EPREFIX}/usr/share/doc/${PF}'"
-	einfo
-	einfo "If you have a newer Intel processor (i5, i7), and you use AES"
-	einfo "you may want to consider using the aes-ni use flag. It will"
-	einfo "use your processors native AES instructions giving quite a speed"
-	einfo "increase."
-	einfo
-}


             reply	other threads:[~2021-10-20  1:51 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20  1:51 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-13  5:56 [gentoo-commits] repo/gentoo:master commit in: sys-fs/loop-aes/ Sam James
2024-08-16 18:48 Arthur Zamarin
2024-05-25  6:50 Sam James
2024-05-25  6:47 Sam James
2024-05-25  6:47 Sam James
2024-05-25  6:47 Sam James
2024-03-04  7:53 Joonas Niilola
2024-01-20 20:18 Mike Pagano
2023-03-23  7:20 Sam James
2023-03-23  7:20 Sam James
2022-12-25 20:06 Sam James
2022-12-25 20:06 Sam James
2022-11-14 14:31 Joonas Niilola
2022-11-14 14:31 Joonas Niilola
2022-07-10 22:51 Sam James
2022-07-10 22:51 Sam James
2021-09-26 21:01 Sam James
2021-09-26 21:01 Sam James
2021-03-13  7:31 Joonas Niilola
2021-03-13  7:31 Joonas Niilola
2020-11-11  7:56 Joonas Niilola
2020-08-08 12:18 Mikle Kolyada
2020-07-20 13:01 Joonas Niilola
2020-06-08 13:41 Joonas Niilola
2020-06-08 13:41 Joonas Niilola
2019-07-08 15:07 Alon Bar-Lev
2019-03-20 22:00 Alon Bar-Lev
2019-03-14 17:30 Alon Bar-Lev
2018-09-27 23:55 Alon Bar-Lev
2018-04-19 22:20 Alon Bar-Lev
2017-12-07 17:40 Alon Bar-Lev
2017-10-07  8:22 Alon Bar-Lev
2017-05-20 17:58 Alon Bar-Lev
2017-03-25 21:46 Alon Bar-Lev
2017-02-04  1:31 Alon Bar-Lev
2016-06-11 16:44 Agostino Sarubbo
2016-05-22 18:37 Alon Bar-Lev
2015-12-23 13:50 Alon Bar-Lev
2015-10-15 14:07 Alon Bar-Lev

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=1634694497.8994a9ab9245a3894d50af4360a2b1fc93510169.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