https://bugzilla.rpmfusion.org/show_bug.cgi?id=908
--- Comment #11 from Jeremy Newton <alexjnewt(a)hotmail.com> 2012-04-30 17:09:12 CEST
---
(In reply to comment #10)
(In reply to comment #9)
> I contacted Ian and asked if I could adopt this. It seems he is very busy and
> say I'm free to adopt this, which I plan to do. Anyway, to my knowledge this is
> still the latest stable, although upstream is still very active. I built this
> just find on my f16 machine so I have no need to change anything unless there
> is issues with f17.
>
> There were no rpmlint errors except a dictionary warning and incorrect FSF
> address errors. I'll contact upstream if this is not fixed in the latest beta.
> As well, I'll look into seeing if the latest beta is feasible to replace this.
> I'm pretty sure there isn't a GUI yet but I plan to look into community
made
> GUI's to see if anything make it's worth replacing version 1.5.
Can we close this ticket as RESOLVED WONTFIX if Ian can't continue this review
request? Jeremy can you open a new ticket with your review request?
Sure but If I don't manage to do it today, I'll have to make it in a few days
because I won't be home or even near a Fedora computer connected to the
internet for that matter. I'll mark this as RESOLVED MOVED and make a comment
referring to the new bug when I make the new request.
Moreover, mupen64plus v1.99.5 is out since last March. Why not
packaging this
version? It has tons of fixes and improvements since v1.5.
The main reason is due to the lack of some prominent features, such as a GUI,
various joystick options, stability, etc. from when I last tried it. I figure
this is because according to the developers, 1.5 is considered the latest
stable, and the 1.9.x series a beta series. I wouldn't mind packaging the beta,
but I'll have to take a look at the latest, along with the available front-ends
to see if the features are fixed or good enough to be worth packaging.
--
Configure bugmail:
https://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.