All of lore.kernel.org
 help / color / mirror / Atom feed
From: cyril Romain <c.romain@laposte.net>
To: Using the OpenEmbedded metadata to build Linux Distributions
	<openembedded-devel@lists.openembedded.org>
Subject: Improve consistency with bittest content checker + sanitize.py
Date: Wed, 13 Sep 2006 20:45:57 +0200	[thread overview]
Message-ID: <450851E5.5060800@laposte.net> (raw)

Following the advice of Holger, I integrated the sanitize.py script into 
the bittest content checker module (at least locally on my machine).
As a reminder:
- bittest is a test suite for bitbake (see the "Bittest advertisement" 
mail). Bittest comes with a "content checker" module able to check the 
*content* of bitbake recipes (the variables and routines used, if theirs 
content is correct and not deprecated, etc.) .
- sanitize.py is aimed to check the *form* of one bitbake recipe, 
according to the rules specified in the format and style guide: 
http://www.openembedded.org/wiki/StyleGuide.

So I think the two complement each other and now provide a "form and 
content" checker for bitbake recipes, a valuable tool to improve the 
metadata consistency.
In addition to the possibility to report test results to Tinderbox 
(http://www.openembedded.org/wiki/TinderBox), bittest is now able to 
send a mail to recipe maintainer when inconsistencies or errors are 
detected, with the sanitized recipe in attachment (that of course may 
still need manual edition).


If you are interested, please let me know.

Thanks Holger for having insisted for me to integrate the script into 
bittest. Thank you, Koen, for the 'send mail' idea.

Best regards,

 Cyril

PS: I also updated the section list in the content checker according to 
the recent discussion.



             reply	other threads:[~2006-09-13 19:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 18:45 cyril Romain [this message]
2006-09-13 19:53 ` Improve consistency with bittest content checker + sanitize.py Koen Kooi
2006-09-13 20:04   ` Paul Sokolovsky
2006-09-13 20:11     ` Koen Kooi
2006-09-13 22:43       ` Michael 'Mickey' Lauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=450851E5.5060800@laposte.net \
    --to=c.romain@laposte.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.