small transistation of a dead upstream game before or after sarge?
I know, we are quite late with this, I know that the "last call for
uploads" has been send a couple of days ago and I know, that the auto
builders are quite busy these days.
That's why I'm quite unsure what to do in this situation.
As you might know, the game tuxracer is dead by upstream, although it
works well, and we could guess that we don't need to touch it again,
when sarge is released (speaking of security updates or such things).
Therefore, there is no real need to touch this package, especially since
it is still fun to play and well known to many people.
But there is ppracer (which I maintain), which is based on tuxracers
code and has an active upstream (which BTW is using Debian, too). The
tuxracer Maintainer - Oliver M. Bolzer <firstname.lastname@example.org> - and I
agree, that ppracer should replace tuxracer sooner or later (see
The open question is: Should we try this transistation right now?
Before Sarge is released?
I'm not sure about that. On the one hand tuxracer still works while
ppracer has not even entered testing, on the other hand I'm wondering if
it serves our users well to still give them old, unmaintained code.
The "plan" for this small transistation would be the following:
- upload a new ppracer which has:
- Replace: tuxracer (< 0.61-6.4)
- Conflicts: tuxracer (< 0.61-6.4)
- Provides: tuxracer
(- has a slighlty changed manpage and icon)
- Leave the rest of the package as it is
- upload an empty tuxracer dummy package (included in ppracer)
- Depends: ppracer
- Long description contains the usual "dummy package, can be removed,
use ppracer instead"
- upload a new tuxracer-extras package (this is maintained by me, just
some extra courses)
This could be ready by tomorror afternoon.
Please note, that although no ppracer version has been built for m68k,
mips or arm, I think they will build fine (they are based on tuxracer,
which works fine, and according to
http://experimental.ftbfs.de/build.php?arch=&pkg=ppracer there have been
succesfull builds on arm and mipsel and the code hasn't been
change since then).
The only tricky thing that I see is, that the new tuxracer-extras should
either not hit sarge before the new ppracer or it should just be renamed
to ppracer-extras (no problem, tuxracer-extras has not been in a stable
release, so no transistation package is needed).
Sorry to take your time with this not very important matter - I'm quite
new in this business ;)