[Bug 43881] New: Make logging TP components easier

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=43881

             Bug #: 43881
           Summary: Make logging TP components easier
    Classification: Unclassified
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: medium
         Component: general
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: guillaume.desmottes at collabora.co.uk
         QAContact: telepathy-bugs at lists.freedesktop.org


I often find myself needing the full logs of a TP component (generally a CM). I
usually manually restart the CM with, say, GABBLE_DEBUG=all
GABBLE_LOGFILE=/tmp/gabble.log and then pray to be able to reproduce the issue
I noticed.

As a Telepathy developer I'm interested in most CMs and may find myself needing
logs from basically as CM. I could tweak my session add define a *_DEBUG and
*_LOGFILE variable for any CM but that's kinda lame and doesn't really scale.

So I'm proposing to add a couple of generic TP variables:
- TP_DEBUG : if the CM specific *_DEBUG variable is not present we use this one
- TP_LOGDIR: if the CM specific *_LOGFILE variable is not present, we log the
debug output to TP_LOGDIR/$cm-name.log

That way I'd just have to define "TP_DEBUG=all TP_LOGDIR=/tmp/telepathy-logs/"
and be done.

Note that would also make debugging easier for bug reporters as they wouldn't
have to play with a billion env variables any more.

So, crack or not?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.