Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Jamie Lenehan <lenehan@twibble.org>
To: Koen Kooi <koen@dominion.kabel.utwente.nl>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: site/* Common site files
Date: Wed, 11 Oct 2006 08:11:07 +1000	[thread overview]
Message-ID: <20061010221107.GB20799@twibble.org> (raw)
In-Reply-To: <452B83DC.2020503@dominion.kabel.utwente.nl>

On Tue, Oct 10, 2006 at 01:28:28PM +0200, Koen Kooi wrote:
[...]
> 
> The consensus is that we want this in OE, how to we proceed to get this added into .dev?

If my implementation was ok then I can push it in over a few days.
The order being:

 - add config_info.bbclass

 - modify recipes that use the site file directly to use config_info instead.

 - update autotools.bbclass to use config_info.bbclass

Then it's ready to actually use. Merging those x86 site files would
be a good place to start.

-- 
 Jamie Lenehan <lenehan@twibble.org>



  reply	other threads:[~2006-10-10 22:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14  0:19 site/* Common site files Jamie Lenehan
2006-10-10 11:28 ` Koen Kooi
2006-10-10 22:11   ` Jamie Lenehan [this message]
2006-10-14 12:34     ` Paul Sokolovsky
2006-11-07 21:24     ` Richard Purdie

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=20061010221107.GB20799@twibble.org \
    --to=lenehan@twibble.org \
    --cc=koen@dominion.kabel.utwente.nl \
    --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