public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Pagano" <mpagano@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-forensics/lynis/
Date: Mon, 16 Dec 2024 21:56:09 +0000 (UTC)	[thread overview]
Message-ID: <1734386156.a7f7d0c29c9df44d4d4f1063624b1b2328c9759d.mpagano@gentoo> (raw)

commit:     a7f7d0c29c9df44d4d4f1063624b1b2328c9759d
Author:     Mike Pagano <mpagano <AT> gentoo <DOT> org>
AuthorDate: Mon Dec 16 21:55:56 2024 +0000
Commit:     Mike Pagano <mpagano <AT> gentoo <DOT> org>
CommitDate: Mon Dec 16 21:55:56 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a7f7d0c2

app-forensics/lynis: add 3.1.3

Signed-off-by: Mike Pagano <mpagano <AT> gentoo.org>

 app-forensics/lynis/Manifest           |  1 +
 app-forensics/lynis/lynis-3.1.3.ebuild | 69 ++++++++++++++++++++++++++++++++++
 2 files changed, 70 insertions(+)

diff --git a/app-forensics/lynis/Manifest b/app-forensics/lynis/Manifest
index 61ee4ee65c17..3e8f7a9c3af5 100644
--- a/app-forensics/lynis/Manifest
+++ b/app-forensics/lynis/Manifest
@@ -1 +1,2 @@
 DIST lynis-3.1.2.tar.gz 355241 BLAKE2B fb224f626d1e42eaaae108a986e4b93fba36b1e6a8ea23208568e3be3dac782f60a9a996ebcc512eaea0234a95e16464a931895b28e3bf8c718ccc8c40126c68 SHA512 e471549898407da3eee58fc404be1e8a166d41e1a527c8d4942882bff60e91554c3a759e08bced7a7c177ccc7a9d7a0b7cad340f3edc3b0e2a39a17302b018ae
+DIST lynis-3.1.3.tar.gz 358461 BLAKE2B 9d955ffd066f8203c9617242a2256a1561b9f99b874486a7d45666871406caf4b3ac3d5f22740171822f6dcbf2ca956d573362dbbd76936fc029df6b376bd1ec SHA512 fb4ad230c3b9d7d47d878da6abda9516d24a02b93235e42044aee2acc0890926028ce0eb947fe47e1705aed4d71080ed08e872c8b6b8592c7128eb80a8f0f002

diff --git a/app-forensics/lynis/lynis-3.1.3.ebuild b/app-forensics/lynis/lynis-3.1.3.ebuild
new file mode 100644
index 000000000000..f294c7a6665f
--- /dev/null
+++ b/app-forensics/lynis/lynis-3.1.3.ebuild
@@ -0,0 +1,69 @@
+# Copyright 1999-2024 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI="8"
+
+inherit bash-completion-r1 systemd
+
+DESCRIPTION="Security and system auditing tool"
+HOMEPAGE="https://cisofy.com/lynis/"
+SRC_URI="https://github.com/CISOfy/${PN}/archive/refs/tags/${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="GPL-3"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+IUSE="+cron systemd"
+
+RDEPEND="
+	app-shells/bash
+	cron? ( !systemd? ( virtual/cron ) )"
+
+src_install() {
+	doman lynis.8
+	dodoc FAQ README
+	newdoc CHANGELOG.md CHANGELOG
+
+	# Remove the old one during the next stabilize progress
+	exeinto /etc/cron.daily
+	newexe "${FILESDIR}"/lynis.cron-new lynis
+
+	dobashcomp extras/bash_completion.d/lynis
+
+	# stricter default perms - bug 507436
+	diropts -m0700
+	insopts -m0600
+
+	insinto /usr/share/${PN}
+	doins -r db/ include/ plugins/
+
+	dosbin lynis
+
+	insinto /etc/${PN}
+	doins default.prf
+	sed -i -e 's/\/path\/to\///' "${S}/extras/systemd/${PN}.service" || die "Sed Failed!"
+	systemd_dounit "${S}/extras/systemd/${PN}.service" || die "Sed Failed!"
+	systemd_dounit "${S}/extras/systemd/${PN}.timer"
+
+	if ! use cron; then
+		ebegin "removing cron files from installation image"
+		rm -rfv "${ED}/etc/cron.daily" || die
+		eend "$?"
+	fi
+}
+
+pkg_postinst() {
+	if use cron; then
+		if systemd_is_booted || has_version sys-apps/systemd; then
+			echo
+			ewarn "Both 'cron' and 'systemd' flags are enabled."
+			ewarn "So both ${PN}.target and cron files were installed."
+			ewarn "Please don't use 2 implementations at the same time."
+			ewarn "Cronjobs are usually enabled by default via /etc/cron.* jobs"
+			ewarn "If you want to use systemd ${PN}.target timers"
+			ewarn "disable 'cron' flag and reinstall ${PN}"
+			echo
+		else
+			einfo "A cron script has been installed to ${ROOT}/etc/cron.daily/lynis."
+		fi
+	fi
+}


             reply	other threads:[~2024-12-16 21:56 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 21:56 Mike Pagano [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-30 23:10 [gentoo-commits] repo/gentoo:master commit in: app-forensics/lynis/ Mike Pagano
2025-01-30 23:10 Mike Pagano
2025-01-01 18:15 Mike Pagano
2024-09-26 19:42 Mike Pagano
2024-09-26 19:42 Mike Pagano
2024-04-18 19:47 Mike Pagano
2024-03-17 14:33 Mike Pagano
2024-03-17 14:33 Mike Pagano
2024-03-11 22:19 Mike Pagano
2024-03-11 22:19 Mike Pagano
2023-12-29 13:05 Mike Pagano
2023-08-04 14:21 Mike Pagano
2023-08-04 14:21 Mike Pagano
2022-10-10 12:42 Mike Pagano
2022-09-01 20:18 Mike Pagano
2022-05-18 11:37 Mike Pagano
2022-05-18 11:37 Mike Pagano
2022-01-20 23:57 Mike Pagano
2022-01-20 23:51 Mike Pagano
2022-01-20 20:19 Mike Pagano
2021-08-09 14:54 Mike Pagano
2021-06-03 16:51 Mike Pagano
2021-03-16 22:40 Sam James
2021-03-16 22:38 Mike Pagano
2021-03-14 12:53 Mike Pagano
2021-01-08 14:21 Mike Pagano
2020-12-25 12:38 Mike Pagano
2020-10-06 15:35 Mike Pagano
2020-07-23 12:57 Mike Pagano
2020-07-12 17:35 Mike Pagano
2020-07-11 15:19 Mike Pagano
2020-07-11 14:55 Mike Pagano
2019-08-27 12:42 Mike Pagano
2019-03-28 12:11 Mike Pagano
2019-02-20 23:44 Mike Pagano
2018-11-27 23:41 Mike Pagano
2018-05-16 14:32 Richard Farina
2017-08-11 17:38 Michał Górny
2017-08-04  6:22 Patrice Clement
2017-08-04  6:22 Patrice Clement
2017-01-06 12:25 Christian Ruppert

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=1734386156.a7f7d0c29c9df44d4d4f1063624b1b2328c9759d.mpagano@gentoo \
    --to=mpagano@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