[tur-users] Unstable (AKA -{svn, cvs, devel}) packages in [community] ?

[Robert Emil Berge]

On Sun, 15 Apr 2007 19:00:54 +0800
"Callan Barrett" <wizzomafizzo at gmail.com> wrote:

> On 4/15/07, Vinay S Shastry <shastry at nidelven-it.no> wrote:
> > On Sunday 15 Apr 2007 4:08:27 pm Pierre Schmitz wrote:
> > > Am Samstag, 14. April 2007 22:01:20 schrieb Alessio 'mOLOk'
> > > Bolognino:
> > > > Do we want to keep those packages out of [community] or what?
> > >
> > > We shouldn`t put svn, git etc. packages into [community]. Those
> > > software is not meant for endusers. Software which is not rleased
> > > yet should stay in [unsupported].
> >
> > I see your point, but TUs don't have access to unstable.
> 
> Spot on Shastry!
> If a TU wants to maintain a development package where else is it going
> to go? There's only the community repo. I don't see the harm in it
> anyway, there's always some demand for packages from
> svn/cvs/git/whatever and why not put them there if someone is willing
> to maintain them? It's not as if you're going to be forced to install
> one of these packages in order to install a stable one.
> 

I think when a package is useful for some people, and a TU wants to
maintain it, it shouldn't be a problem to have it in [community]. For
very many programs scm versions aren't unstable at all, they are often
more stable than the last release, and contain useful new features.
Many developers are busy developing and sometimes it takes years
between stable releases, and the developers just tell people to use the
svn, cvs etc. version.
I maintain kdenlive, and decided to use mtl-cvs instead of the last
release of mlt, since it's what the developers recomend and it is
needed for the latest effects.

 - filoktetes