[mythtv] What can packagers/distro developers do to help the stability of "released" version of MythTV?

Johnny Strom jonny.strom at netikka.fi
Thu Feb 24 09:24:50 UTC 2005


Adam Egger wrote:
> On Wed, 23 Feb 2005 17:37:35 -0800, Nav Jagpal <nav.jagpal at gmail.com> wrote:
> 
> 
>>For example, Debian has three "branches" (Don't think that's the right
>>word for it).. Stable/testing/unstable. That may be overkill for this
>>project, but the idea is there.
> 
> 
> So the easiest solution for the packagers/distro developers is to
> create ~weekly experimental packages when something important was
> commited to cvs.
> So there would be official release packages *and* experimental packages. 
> There's no really a need to have three "branches" like in debian. You
> don't even need the stable "branch" for mythtv because CVS is really
> "mostlystable". But it would help people to get back to a working
> branch if something's really unusable in CVS (with a dbdump of
> course).
> And then just 
> apt-get install mythtv  - to get releases (0.17) or
> apt-get install -t experimental mythtv - to get cvs builds (0.17.20050224).
> 

Hi

Yes this is good idea to build packages from cvs perhaps make a script 
that dose it automatically every night.




> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev



More information about the mythtv-dev mailing list