From mboxrd@z Thu Jan  1 00:00:00 1970
From: garoth@gmail.com (Andrei Thorp)
Date: Mon, 17 Aug 2009 16:31:22 -0400
Subject: [sup-talk] logging and internal API changes in next
In-Reply-To: <1250538107-sup-7121@masanjin.net>
References: <1250538107-sup-7121@masanjin.net>
Message-ID: <1250541071-sup-7690@Longbow>

Excerpts from William Morgan's message of Mon Aug 17 15:50:52 -0400 2009:
> Dear Suppers,
> 
> I've merged the aforementioned internal API changes, and a pretty big
> rewrite of the logging system (branch "logging"), into next. It works
> for me, but please report any problems you see.
> 
> All logging messages are now categorized by level (debug, info, warn,
> error) and will only be output when the global logging level is <= the
> message level. The global logging level is determined by the environment
> variable SUP_LOG_LEVEL; when unset, the default is "info". You'll notice
> that the majority of the messages you saw before are now "debug"
> messages, so the log buffer is much quieter.
> 
> This change also applies to the various sup-* scripts.
> 
> If you use this code and then switch to a branch without these changes,
> you may encounter errors because labels are now represented on disk as
> Sets instead of arrays. The solution is to edit your sources.yaml file
> and manually change the Sets back to arrays; it should be obvious how to
> do this. I don't anticipate this affecting too many people. If it does,
> we can transform labels to arrays before storing to make this easier,
> but hopefully it's just a temporary issue.
> 
> I would like to merge these changes down to master sooner rather than
> later, because they're so far-reaching.

Looking forward to it, thanks.
-- 
Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com)