> As stated above the mplayer team does not do releases and recommends
> using SVN. I know this causes more work for you as a packager, but even
> doing a monthly or quarterly release even with a package name of
> 'mplayer-svn' would be helpful. That way the people that want a 'stable'
> mplayer can use mplayer and those that want one that actually works, can
> track a newer package.
The documented procedure is to update the package first in the unstable
branch of ubuntu (currently jaunty) and then have it included in the
-backports repository.
Introducing mplayer-svn would introduce an inappropriate additional
maintenance overhead.
Kevin DeKorte <email address hidden> writes:
> As stated above the mplayer team does not do releases and recommends
> using SVN. I know this causes more work for you as a packager, but even
> doing a monthly or quarterly release even with a package name of
> 'mplayer-svn' would be helpful. That way the people that want a 'stable'
> mplayer can use mplayer and those that want one that actually works, can
> track a newer package.
The documented procedure is to update the package first in the unstable
branch of ubuntu (currently jaunty) and then have it included in the
-backports repository.
Introducing mplayer-svn would introduce an inappropriate additional
maintenance overhead.
--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4