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: Sat, 25 May 2024 06:47:29 +0000 (UTC)	[thread overview]
Message-ID: <1716619608.d7c7c96343e5080714b03d00112b06706f3e02ce.sam@gentoo> (raw)

commit:     d7c7c96343e5080714b03d00112b06706f3e02ce
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat May 25 06:41:30 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat May 25 06:46:48 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d7c7c963

sys-fs/loop-aes: tweak style

Group *DEPEND together, put eclass var pre-inherit.

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

 sys-fs/loop-aes/loop-aes-3.8c.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sys-fs/loop-aes/loop-aes-3.8c.ebuild b/sys-fs/loop-aes/loop-aes-3.8c.ebuild
index 5c3b2d38850a..00e492cdf3b0 100644
--- a/sys-fs/loop-aes/loop-aes-3.8c.ebuild
+++ b/sys-fs/loop-aes/loop-aes-3.8c.ebuild
@@ -3,6 +3,7 @@
 
 EAPI=8
 
+VERIFY_SIG_OPENPGP_KEY_PATH="/usr/share/openpgp-keys/jariruusu.asc"
 inherit linux-mod-r1 verify-sig
 
 MY_P="${PN/aes/AES}-v${PV}"
@@ -16,8 +17,6 @@ SRC_URI="
 			-> ${MY_P}.tar.bz2.sig
 	)
 "
-BDEPEND="verify-sig? ( sec-keys/openpgp-keys-jariruusu )"
-VERIFY_SIG_OPENPGP_KEY_PATH="/usr/share/openpgp-keys/jariruusu.asc"
 S="${WORKDIR}/${MY_P}"
 
 LICENSE="GPL-2"
@@ -26,6 +25,7 @@ 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"
+BDEPEND="verify-sig? ( sec-keys/openpgp-keys-jariruusu )"
 
 PATCHES=(
 	"${FILESDIR}"/loop-aes-3.7w-build-initrd_explicit-losetup.patch


             reply	other threads:[~2024-05-25  6:47 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-25  6:47 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-16 18:48 [gentoo-commits] repo/gentoo:master commit in: sys-fs/loop-aes/ Arthur Zamarin
2024-05-25  6:50 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-10-20  1: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=1716619608.d7c7c96343e5080714b03d00112b06706f3e02ce.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