2 Apr
2012
2 Apr
'12
3:44 p.m.
On 2 April 2012 11:36, Darrell Anderson <humanreadable(a)yahoo.com> wrote:
I just noticed that this bug (845) was assigned to me. I have no
intention or any idea how to fix xine backends. :) someone else
interested?
Calvin
I am always
amazed by the amount of text konsole
retains in its history when set to unlimited.
Use tee and logs. :) My master build script (the one script to build everything) has a
function to tee the output to a log file. When I build a single package, then I manually
run like this:
./buildscript | tee build.log
No scrolling of the terminal required. Just browse the text log.
If you have a quick fix for this one -- let me
know
what you did so I can learn how to solve these. If not, can you point me to one of
your prior patches that did this so I can take a look. I think we just did one
of these within the past week where you did the patch, but I can't recall what
package it was on. (age)
I believe you are referring to the thread you started about amarok. I don't remember
the solution, but the problem is newer versions of xine. Check bug report 845 and look at
the list archives using a search term of 'const'.
http://trinity-devel.pearsoncomputing.net/?0:::search
Darrell