public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: games-emulation/m64py/
Date: Mon,  1 Jan 2018 13:47:38 +0000 (UTC)	[thread overview]
Message-ID: <1514814448.61d1d501c258d1957c29852eb1557a1401e4fd3c.mgorny@gentoo> (raw)

commit:     61d1d501c258d1957c29852eb1557a1401e4fd3c
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Mon Jan  1 13:33:48 2018 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Mon Jan  1 13:47:28 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=61d1d501

games-emulation/m64py: Remove obsolete upgrade notice

 games-emulation/m64py/m64py-0.2.4.ebuild | 17 +----------------
 1 file changed, 1 insertion(+), 16 deletions(-)

diff --git a/games-emulation/m64py/m64py-0.2.4.ebuild b/games-emulation/m64py/m64py-0.2.4.ebuild
index 67f1a08e394..f9e3dece457 100644
--- a/games-emulation/m64py/m64py-0.2.4.ebuild
+++ b/games-emulation/m64py/m64py-0.2.4.ebuild
@@ -5,7 +5,7 @@ EAPI=5
 
 PYTHON_COMPAT=( python3_{4,5} )
 
-inherit distutils-r1 versionator xdg-utils
+inherit distutils-r1 xdg-utils
 
 DESCRIPTION="A frontend for Mupen64Plus"
 HOMEPAGE="http://m64py.sourceforge.net/"
@@ -34,21 +34,6 @@ _EOF_
 pkg_postinst() {
 	xdg_desktop_database_update
 
-	local vr
-	for vr in ${REPLACING_VERSIONS}; do
-		if ! version_is_at_least 0.2.1-r1 ${vr}; then
-			ewarn
-			ewarn "Starting with mupen64plus-2.0-r1, the plugin install path has changed."
-			ewarn "In order for m64py to find mupen64plus, you will either need to set"
-			ewarn "new paths in configuration dialog or remove your configuration file."
-			ewarn "The new paths are:"
-			ewarn
-			ewarn " Library file:      /usr/$(get_libdir)/libmupen64plus.so.2.0.0"
-			ewarn " Plugins directory: /usr/$(get_libdir)/mupen64plus"
-			ewarn " Data directory:    /usr/share/mupen64plus"
-		fi
-	done
-
 	if ! type -P rar >/dev/null && ! type -P unrar >/dev/null; then
 		elog
 		elog "In order to gain RAR archive support, please install either app-arch/rar"


             reply	other threads:[~2018-01-01 13:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-01 13:47 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-19 15:24 [gentoo-commits] repo/gentoo:master commit in: games-emulation/m64py/ Michał Górny
2024-05-28 15:27 Michał Górny
2023-11-27 12:31 Michał Górny
2023-04-08 13:40 Michał Górny
2023-04-08 13:40 Michał Górny
2023-04-08 13:40 Michał Górny
2023-03-09  7:38 Arthur Zamarin
2022-05-18 10:29 Michał Górny
2022-05-18  7:36 Michał Górny
2020-09-18  9:38 Michał Górny
2020-08-01 22:10 Aaron Bauman
2020-07-12  6:37 Michał Górny
2020-07-12  6:37 Michał Górny
2020-01-03 20:40 Michał Górny
2019-06-16 17:59 David Seifert
2018-03-26 16:14 Michał Górny
2018-01-01 13:47 Michał Górny
2018-01-01 13:47 Michał Górny
2018-01-01 13:47 Michał Górny
2018-01-01 13:47 Michał Górny
2018-01-01 13:47 Michał Górny
2016-10-08  6:29 Pacho Ramos
2016-06-11 20:39 Pacho Ramos
2016-03-27 17:44 David Seifert
2015-10-25 21:36 Michał Górny
2015-10-04  9:40 Michał Górny

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=1514814448.61d1d501c258d1957c29852eb1557a1401e4fd3c.mgorny@gentoo \
    --to=mgorny@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