[Dehs-devel] SVN devscripts commit: r225 - in trunk: . debian

[Julian Gilbey]

On Mon, Aug 15, 2005 at 03:02:48PM +0200, Filippo Giunchedi wrote:
> I was thinking about changing --dehs behaviour of uscan to something like
> --machine-parsable, xml output is fine but since the data/output is not
> structured, xml is overkill. Maybe something like:
> 
> <one_letter_code>: message
> 
> with the code being W,E,I or whatever (yes, this is rfc822) and the message
> being the output.
> This would include reworking uscan's output functions to switch between "normal"
> messages and machine-parsable ones.
> 
> any comment/suggestion?
> filippo

Haven't we been here before:

On Wed, Mar 23, 2005 at 11:29:56AM +0100, Filippo Giunchedi wrote:
> On Tue, Mar 22, 2005 at 10:00:31PM +0000, Julian Gilbey wrote:
> > > attached there is the (rather trivial) patch for uscan for using rfc882-style
> > > messages (maybe xml is overkill, the data is not structured)
> > 
> > Unfortunately the patch will not produce valid rfc822-style output, as
> > some fields may be more than one line long.  Given the ease of parsing
> > XML output these days, and the fact that there are so many tools
> > available for doing so, why would we want to regress to rfc822-style
> > output?  Not to mention that other people may make use of this output
> > format.
> 
> indeed I didn't thought at multiline output, so let's use XML (and maybe change
> this thread name or open a new one ;))

   Julian