[mythtv-users] Is this correct to get the GIT for 26 fixes?

[R. G. Newbury]

On 2012-10-27, at 10:28 AM, Mark <markhsa at gmail.com> wrote:

> On 2012-10-26 5:50 PM, R. G. Newbury wrote:
>> On 10/26/2012 02:16 PM, Richard Shaw wrote:
>>> On Fri, Oct 26, 2012 at 1:14 PM, Mark<markhsa at gmail.com>  wrote:
>>>> I do want to and currently am yes.  I am on F17 and there are no repos yet
>>>> that I know of.
>>> 
>>> RPM Fusion has 0.25.2. I'm going to be pushing 0.26 packages soonish
>>> (when I have time). The packages do a HUGE amount of work for you so
>>> even if you want to build yourself I would highly recommend using the
>>> source RPM instead of doing everything from scratch.
>> 
>> All of the packages in the mythtv meta-package on ATRPMS are dated October 14. .026 was released October 3rd.
>> 
>> The packages would not be 'fixes' but are .26 on ATRPMS.
>> 
>> Instead of fixes you could try master:
>> 
>> git clone git://github.com/MythTV/mythtv.git mythtv
>> 
>> G
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://www.mythtv.org/mailman/listinfo/mythtv-users
> Is master not the development for the coming 27 release?  So they would be cutting edge and probably not daily use ready.  Or am I wrong on this?

No you are not. But 'daily fixes' is just master aged a little to see if there are any regressions which were not immediately visible.
If you are pulling fixes or master why are you bothering to build rpms? The patches etc are already in the repo. Do 'rm clonefolder' 'git clone' ' cd clone' configure  && make && make install' . Obviously the first couple of tries will expose any deficiencies in setup but after that you can do it by script straight through. If you can build an rpm you can compile instead. 

G