Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Klaus Schwarzkopf <schwarzkopf@sensortherm.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: buildserver
Date: Sat, 20 Nov 2010 14:49:38 +0100	[thread overview]
Message-ID: <4CE7D1F2.7010305@sensortherm.de> (raw)
In-Reply-To: <AANLkTinAj4fG48Ppz_jwT1nmp+tzntZ9YJPaqat4HbES@mail.gmail.com>


> Other good idea is to have sanity checker running once per day too. It
> may do next things:
> - check recipes syntax
> - check thath recipes SRC_URI can be fetched

I think, bitbake can easily integrate this two features.

For example the new options:

--download-only 		only download the source files for the given recipe

--download-only-with-depencies  only download the source files for the 
given recipe and its depencies

--check-syntax			check recipes syntax	


What do you think?

Greetings,

Klaus


> - check recipes for security flaws (we have tool already)
> - ...
> - PROFIT! :) (sorry, just can't not to write this :)
>




  parent reply	other threads:[~2010-11-20 13:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19  9:46 buildserver Klaus Schwarzkopf
2010-11-19 10:37 ` buildserver Koen Kooi
2010-11-19 11:48   ` buildserver Klaus Schwarzkopf
2010-11-20 13:29   ` buildserver Klaus Schwarzkopf
2010-11-19 10:42 ` buildserver Yury Bushmelev
2010-11-19 11:24   ` buildserver Martin Jansa
2010-11-19 12:21     ` buildserver Frans Meulenbroeks
2010-11-19 11:55   ` buildserver Klaus Schwarzkopf
2010-11-19 12:04   ` buildserver Dvorkin Dmitry
2010-11-20 13:49   ` Klaus Schwarzkopf [this message]
2010-11-21 18:08     ` buildserver Chris Larson
2010-11-22  8:38       ` buildserver Klaus Schwarzkopf
2010-11-22  8:56         ` buildserver Frans Meulenbroeks
2010-11-22 15:14           ` buildserver Klaus Schwarzkopf
2010-11-22 17:25             ` buildserver Frans Meulenbroeks
2010-11-22 17:31               ` buildserver Eric Bénard
2010-11-22 18:21                 ` buildserver Frans Meulenbroeks
2010-11-22 18:41                   ` buildserver Eric Bénard

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=4CE7D1F2.7010305@sensortherm.de \
    --to=schwarzkopf@sensortherm.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox