From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/nagios-icinga-openvpn/
Date: Mon, 20 Apr 2020 13:26:38 +0000 (UTC) [thread overview]
Message-ID: <1587389116.289868cbcb594dbb116a08ba1cc2270495c45970.mjo@gentoo> (raw)
commit: 289868cbcb594dbb116a08ba1cc2270495c45970
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 20 13:24:59 2020 +0000
Commit: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Mon Apr 20 13:25:16 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=289868cb
net-analyzer/nagios-icinga-openvpn: new revision for newer pythons.
Also with an EAPI=7 update. Nothing else changed.
Closes: https://bugs.gentoo.org/718422
Package-Manager: Portage-2.3.89, Repoman-2.3.20
Signed-off-by: Michael Orlitzky <mjo <AT> gentoo.org>
.../nagios-icinga-openvpn-0.0.1-r1.ebuild | 38 ++++++++++++++++++++++
1 file changed, 38 insertions(+)
diff --git a/net-analyzer/nagios-icinga-openvpn/nagios-icinga-openvpn-0.0.1-r1.ebuild b/net-analyzer/nagios-icinga-openvpn/nagios-icinga-openvpn-0.0.1-r1.ebuild
new file mode 100644
index 00000000000..a03ce2d5c4d
--- /dev/null
+++ b/net-analyzer/nagios-icinga-openvpn/nagios-icinga-openvpn-0.0.1-r1.ebuild
@@ -0,0 +1,38 @@
+# Copyright 1999-2020 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+PYTHON_COMPAT=( python3_6 python3_7 python3_8 )
+DISTUTILS_USE_SETUPTOOLS=no
+inherit distutils-r1
+
+MY_PN="check_openvpn"
+DESCRIPTION="A Nagios plugin to check whether an OpenVPN server is alive"
+HOMEPAGE="https://github.com/liquidat/nagios-icinga-openvpn"
+SRC_URI="https://github.com/liquidat/nagios-icinga-openvpn/archive/${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64"
+IUSE=""
+
+src_install() {
+ distutils-r1_src_install
+
+ local nagiosplugindir="/usr/$(get_libdir)/nagios/plugins"
+ dodir "${nagiosplugindir}"
+
+ # Create a symlink from the nagios plugin directory to the /usr/bin
+ # location. The "binary" in /usr/bin should also be a symlink, since
+ # the python machinery allows the user to switch out the
+ # interpreter. We don't want to mess with any of that, so we just
+ # point to whatever the system would use if the user executed
+ # ${MY_PN}.
+ #
+ # The relative symlink is preferred so that if the package is
+ # installed e.g. while in a chroot, the symlink will never point
+ # outside of that chroot.
+ #
+ dosym "../../../bin/${MY_PN}" "${nagiosplugindir}/${MY_PN}"
+}
next reply other threads:[~2020-04-20 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 13:26 Michael Orlitzky [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-14 11:43 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/nagios-icinga-openvpn/ Michael Orlitzky
2023-04-19 12:35 Michael Orlitzky
2023-04-19 12:35 Michael Orlitzky
2023-02-25 17:41 Michael Orlitzky
2023-02-25 17:41 Michael Orlitzky
2021-09-28 14:07 Michael Orlitzky
2021-09-26 5:01 Sam James
2021-07-30 3:21 Sam James
2021-07-30 1:09 Michael Orlitzky
2020-05-13 13:32 Michael Orlitzky
2020-05-13 13:32 Michael Orlitzky
2020-02-11 12:16 Michał Górny
2020-02-08 18:55 David Seifert
2019-05-07 0:31 Michael Orlitzky
2018-08-16 11:45 Michael Orlitzky
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=1587389116.289868cbcb594dbb116a08ba1cc2270495c45970.mjo@gentoo \
--to=mjo@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