http://bugzilla.rpmfusion.org/show_bug.cgi?id=1572
--- Comment #4 from Hans de Goede <[email protected]> 2011-01-06 13:49:21 --- Hi, Thanks for the review! (In reply to comment #3) > === Issues === > 1. Same content i muliple subpackages (see above) This is intentional, these files are very small, and as long as they are identical between versions (which they are) rpm will not raise file conflict errors (this is also how things work with header files with multilib -devel packages). Given the small size of the shared files I don't think that doing a -common subpackage is worth it. > 2. URL / Source0 URL need to be updated to new upstream location Will do. > 3. Maybe update to latest upstream release. Well the original upstream is dead and has gone 404 (dropped of the net) a few days before I finished packaging this. It looks like Chris Ballinger is continuing from where the original upstream left, taking the latest svn snapshot from the original upstream and doing a 1.7 released based on that. I've been working on packaging wolf4sdl together with Fabian Greffrath from Debian we we're planning on starting a new upstream at sourceforge.net to have a VCS to integrate our patches (and a bugtracker and a place to do new releases), but then discovered about Chris Ballinger's work 2 days ago. We've contacted Chris to work together with him to start a new upstream (including a VCS, bugtracker, etc.). We're awaiting an answer from Chris atm. So I would like to stay with the proven (unchanged for ages) 1.6 version and then move to a newer upstream version once a new upstream has been established. ### If you're ok with my answers to 1. and 3. I'll do a new version fixing 2. -- Configure bugmail: http://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.
