thanks for that explanations! Here is the changelog entry I will upload:
sdlmame (0.136-0ubuntu1) lucid; urgency=low
* New upstream release - Closes (LP: #502191)
* debian/rules:
- Added new make variable NOASM to take advantage of the Assembly core when
available, and also mandatory on some targets (ARM, for example)
- Get whatsnew.txt from MAME site in get-orig-source target as it's missing
in upstream tarball
* debian/sdlmame.1: updated with new options "listdevices" and "numprocessors"
* debian/contrib/config/joymap.dat: deleted for obsolete as joystick code is not
based on SDL anymore
I only have one concern with the whatsnew.txt file, as I think it should be part of the debian directory, and not put in the upstream tarball during the get-orig-source steps. What do you think? This way, you would have, and install, the whatnew.txt file in debian directory.
Hi Cesare,
thanks for that explanations! Here is the changelog entry I will upload:
sdlmame (0.136-0ubuntu1) lucid; urgency=low
* New upstream release - Closes (LP: #502191) contrib/ config/ joymap. dat: deleted for obsolete as joystick code is not
* debian/rules:
- Added new make variable NOASM to take advantage of the Assembly core when
available, and also mandatory on some targets (ARM, for example)
- Get whatsnew.txt from MAME site in get-orig-source target as it's missing
in upstream tarball
* debian/sdlmame.1: updated with new options "listdevices" and "numprocessors"
* debian/
based on SDL anymore
-- Cesare Falco <email address hidden> Sun, 03 Jan 2010 15:39:00 +0100
I only have one concern with the whatsnew.txt file, as I think it should be part of the debian directory, and not put in the upstream tarball during the get-orig-source steps. What do you think? This way, you would have, and install, the whatnew.txt file in debian directory.
Thanks,
Fabrice