From: "Manuel Rueger (mrueg)" <mrueg@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in kde-base/ksysguard: ksysguard-4.11.20.ebuild ChangeLog
Date: Wed, 3 Jun 2015 23:04:53 +0000 (UTC) [thread overview]
Message-ID: <20150603230453.4DD07A30@oystercatcher.gentoo.org> (raw)
mrueg 15/06/03 23:04:53
Modified: ChangeLog
Added: ksysguard-4.11.20.ebuild
Log:
Version bump.
(Portage version: 2.2.20/cvs/Linux x86_64, signed Manifest commit with key )
Revision Changes Path
1.354 kde-base/ksysguard/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/kde-base/ksysguard/ChangeLog?rev=1.354&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/kde-base/ksysguard/ChangeLog?rev=1.354&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/kde-base/ksysguard/ChangeLog?r1=1.353&r2=1.354
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/kde-base/ksysguard/ChangeLog,v
retrieving revision 1.353
retrieving revision 1.354
diff -u -r1.353 -r1.354
--- ChangeLog 15 May 2015 15:53:06 -0000 1.353
+++ ChangeLog 3 Jun 2015 23:04:53 -0000 1.354
@@ -1,6 +1,11 @@
# ChangeLog for kde-base/ksysguard
# Copyright 1999-2015 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/kde-base/ksysguard/ChangeLog,v 1.353 2015/05/15 15:53:06 kensington Exp $
+# $Header: /var/cvsroot/gentoo-x86/kde-base/ksysguard/ChangeLog,v 1.354 2015/06/03 23:04:53 mrueg Exp $
+
+*ksysguard-4.11.20 (03 Jun 2015)
+
+ 03 Jun 2015; Manuel Rüger <mrueg@gentoo.org> +ksysguard-4.11.20.ebuild:
+ Version bump.
*ksysguard-4.11.19 (15 May 2015)
1.1 kde-base/ksysguard/ksysguard-4.11.20.ebuild
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/kde-base/ksysguard/ksysguard-4.11.20.ebuild?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/kde-base/ksysguard/ksysguard-4.11.20.ebuild?rev=1.1&content-type=text/plain
Index: ksysguard-4.11.20.ebuild
===================================================================
# Copyright 1999-2015 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/kde-base/ksysguard/ksysguard-4.11.20.ebuild,v 1.1 2015/06/03 23:04:53 mrueg Exp $
EAPI=5
KDE_HANDBOOK="optional"
KMNAME="kde-workspace"
CPPUNIT_REQUIRED="optional"
VIRTUALX_REQUIRED="test"
inherit kde4-meta
DESCRIPTION="KSysguard is a network enabled task manager and system monitor application"
HOMEPAGE+=" http://userbase.kde.org/KSysGuard"
KEYWORDS="~amd64 ~arm ~ppc ~ppc64 ~x86 ~amd64-linux ~x86-linux"
IUSE="debug lm_sensors test"
DEPEND="
sys-libs/zlib
x11-libs/libX11
x11-libs/libXres
lm_sensors? ( sys-apps/lm_sensors )
"
RDEPEND="${DEPEND}"
RESTRICT="test"
# bug 393091
KMEXTRA="
libs/ksysguard/
"
src_configure() {
local mycmakeargs=(
$(cmake-utils_use_with lm_sensors Sensors)
)
kde4-meta_src_configure
}
pkg_postinst() {
kde4-meta_pkg_postinst
ewarn "Note that ksysguard has powerful features; one of these is the executing of arbitrary"
ewarn "programs with elevated privileges (as data sources). So be careful opening worksheets"
ewarn "from untrusted sources!"
}
reply other threads:[~2015-06-03 23:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150603230453.4DD07A30@oystercatcher.gentoo.org \
--to=mrueg@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