From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-portage/elogviewer/
Date: Sat, 1 Aug 2020 23:20:00 +0000 (UTC) [thread overview]
Message-ID: <1596323975.ad8380a95dee948a3a372f3d13ab0660e9669368.asturm@gentoo> (raw)
commit: ad8380a95dee948a3a372f3d13ab0660e9669368
Author: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Sat Aug 1 15:19:13 2020 +0000
Commit: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Sat Aug 1 23:19:35 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ad8380a9
app-portage/elogviewer: Drop 2.9-r1
Package-Manager: Portage-3.0.1, Repoman-2.3.23
Signed-off-by: Andreas Sturmlechner <asturm <AT> gentoo.org>
app-portage/elogviewer/Manifest | 1 -
app-portage/elogviewer/elogviewer-2.9-r1.ebuild | 66 -------------------------
2 files changed, 67 deletions(-)
diff --git a/app-portage/elogviewer/Manifest b/app-portage/elogviewer/Manifest
index d782e287505..df98e588981 100644
--- a/app-portage/elogviewer/Manifest
+++ b/app-portage/elogviewer/Manifest
@@ -1,2 +1 @@
-DIST elogviewer-2.9.tar.gz 24157 BLAKE2B ff527c0198e86f7be15fce3f25f0e9677b6911cef72cfdc1f582c62f534fc15adac8c2cf612475f174561dd46b489dcaf819c8ccd1b5893adeb7a6c085ce11c2 SHA512 e5781eeaf663fafa680b0620c4a6aec63afffd05c1cb4cb5362e9eca3a35c85550ee295a6b753155b0392d69442068cf155c3ead872c457e5a3cdbcd59b1ab2e
DIST elogviewer-3.0.tar.gz 28349 BLAKE2B 44f3ca5b28d075bb8349450cc817fd8ccdd1d1dc7eb948a9d65ab3b423191eca04cc479b2d6bec0bf6bc7f1120eccd257fdf61bb736919129ee756c2f4bd4366 SHA512 7eb59849a06632053ee0f7d1d76d9848220dbb8ad48d04c80fea5e64304f86c1a99987f525c6df682c832bd8453e07781a5c95ad2dee0539e954400730f47e36
diff --git a/app-portage/elogviewer/elogviewer-2.9-r1.ebuild b/app-portage/elogviewer/elogviewer-2.9-r1.ebuild
deleted file mode 100644
index d4455cc879c..00000000000
--- a/app-portage/elogviewer/elogviewer-2.9-r1.ebuild
+++ /dev/null
@@ -1,66 +0,0 @@
-# Copyright 1999-2020 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=6
-
-PYTHON_COMPAT=( python3_6 )
-
-DISABLE_AUTOFORMATTING=true
-
-inherit python-single-r1 eutils readme.gentoo-r1
-
-DESCRIPTION="Elog viewer for Gentoo"
-HOMEPAGE="https://sourceforge.net/projects/elogviewer"
-SRC_URI="https://github.com/Synss/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
-
-LICENSE="GPL-2"
-SLOT="0"
-KEYWORDS="amd64 ~ppc x86"
-IUSE=""
-REQUIRED_USE="${PYTHON_REQUIRED_USE}"
-
-RDEPEND="${PYTHON_DEPS}
- $(python_gen_cond_dep '
- dev-python/PyQt5[gui,widgets,${PYTHON_MULTI_USEDEP}]
- >=sys-apps/portage-2.1[${PYTHON_MULTI_USEDEP}]
- ')
- $(python_gen_cond_dep 'dev-python/enum34[${PYTHON_MULTI_USEDEP}]' python2_7)
-"
-DEPEND="${RDEPEND}
- $(python_gen_cond_dep '
- dev-python/setuptools[${PYTHON_MULTI_USEDEP}]
- ')
-"
-
-DOC_CONTENTS="In order to use this software, you need to activate
-Portage's elog features. Required is
- PORTAGE_ELOG_SYSTEM=\"save\"
-and at least one of
- PORTAGE_ELOG_CLASSES=\"warn error info log qa\"
-More information on the elog system can be found in
-/usr/share/portage/config/make.conf.example
-
-To operate properly this software needs the directory
-${PORT_LOGDIR:-/var/log/portage}/elog created, belonging to group portage.
-To start the software as a user, add yourself to the portage group."
-
-src_compile() {
- rm -f Makefile
-}
-
-src_install() {
- python_newscript elogviewer.py elogviewer
-
- make_desktop_entry ${PN} ${PN} ${PN} System
-
- doman elogviewer.1
- readme.gentoo_create_doc
-}
-
-pkg_postinst() {
- readme.gentoo_print_elog
-
- ewarn "The elogviewer's configuration file is now saved in:"
- ewarn "~/.config/elogviewer/ (was ~/.config/Mathias\ Laurin/)."
- ewarn "Please migrate any user specific settings to the new config file."
-}
next reply other threads:[~2020-08-01 23:20 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 23:20 Andreas Sturmlechner [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-14 13:39 [gentoo-commits] repo/gentoo:master commit in: app-portage/elogviewer/ Arthur Zamarin
2025-02-14 13:35 Arthur Zamarin
2025-02-14 13:34 Arthur Zamarin
2025-02-14 13:34 Arthur Zamarin
2024-06-06 0:45 Sam James
2024-06-06 0:45 Sam James
2023-03-05 15:22 Sam James
2022-05-22 16:13 Zac Medico
2021-05-27 6:57 Agostino Sarubbo
2021-05-27 6:55 Agostino Sarubbo
2021-02-28 13:05 Ben Kohler
2021-02-24 13:55 Ben Kohler
2020-08-01 23:20 Andreas Sturmlechner
2020-05-10 8:20 Brian Dolbec
2020-02-10 11:54 Michał Górny
2020-01-07 17:02 Ben Kohler
2019-09-14 5:18 Matt Turner
2019-05-18 10:02 Michał Górny
2018-06-24 13:09 Jason Zaman
2018-06-23 10:02 Pacho Ramos
2018-06-08 18:35 Andreas Sturmlechner
2018-06-08 18:35 Andreas Sturmlechner
2018-05-10 15:46 Brian Dolbec
2018-05-10 14:49 Andreas Sturmlechner
2018-03-21 18:12 Michał Górny
2018-03-21 18:12 Michał Górny
2017-09-02 14:50 Michael Palimaka
2017-08-05 8:10 Michael Palimaka
2017-07-15 15:17 Tobias Klausmann
2017-04-20 7:59 David Seifert
2017-03-10 14:26 Michael Weber
2016-12-24 21:54 Brian Dolbec
2016-05-22 10:37 Ian Delaney
2016-05-22 10:37 Ian Delaney
2015-12-03 10:07 Agostino Sarubbo
2015-12-02 18:23 Paul Varner
2015-11-12 9:40 Agostino Sarubbo
2015-11-11 9:12 Agostino Sarubbo
2015-11-09 10:31 Agostino Sarubbo
2015-09-11 5:40 Brian Dolbec
2015-09-11 5:26 Brian Dolbec
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=1596323975.ad8380a95dee948a3a372f3d13ab0660e9669368.asturm@gentoo \
--to=asturm@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