Summary: | games-misc/mednaffe-0.6 - GTK+ front-end for games-emulation/mednafen | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Samuel Bauer <samuel.bauer> |
Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | games |
Priority: | Normal | Keywords: | EBUILD |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://code.google.com/p/mednaffe/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
mednaffe-0.6.ebuild
updated ebuild for Version 0.8 |
Created attachment 421538 [details]
updated ebuild for Version 0.8
Why the debugger use flag on mednafen? Because mednaffe-0.8 uses a command-line option which does not exist without. And then mednafen not be started. games-emulation/mednaffe/mednaffe-0.8.ebuild is in portage. |
Created attachment 374708 [details] mednaffe-0.6.ebuild a gtk+ front end for mednafen only compatible with >=mednafen-0.9.30 when >=mednafen-0.9.30 has never been launched, front end will complain about deprecated mednafen version, because of the missing configuration file. A pre-requisite is to launch new mednafen version before mednaffe, perhaps the ebuild should warn through elog.