So far it's been the gentoo and arch linux users who've had the mysql5 problem... probably because those distros have that in their main package channel.
But I really have no idea how one would go about fixing the problem... the log files are utterly unhelpful (works one minute, dies the next, no message), as are the debugging programs. Anyway, I've got a paradox happening on my system... on the one hand I need mysql5 for rails and php. On the other, I need mysql4 for myth. Oh crap. On 12/27/05, Jarod Wilson <[EMAIL PROTECTED]> wrote: > On Tuesday 27 December 2005 17:27, Nigel Pearson wrote: > > > Certainly, though in looking at the changes in the latest > > > checksetup.cpp (7780), should I be using that, or the prior 7778? > > > Looks like 7780 might be changes for the > > > new way live TV is handled in the trunk... > > > > Sorry, yes you are right. Make that: > > > > /trunk/mythtv/setup/checksetup.cpp?rev=7778 > > /trunk/mythtv/setup/checksetup.h > > /trunk/mythtv/setup/main.cpp?rev=6609 (or newer?) > > I'll go with 6698 for main.cpp to get the basic functionality plus the verbose > option patch. Later revisions get a bit more invasive, touching additional > files. Just committed... > > -- > Jarod Wilson > [EMAIL PROTECTED] > > > _______________________________________________ > mythtv-dev mailing list > mythtv-dev@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev > > > > _______________________________________________ mythtv-dev mailing list mythtv-dev@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
