All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Jamie Lenehan <lenehan@twibble.org>
Cc: Using the OpenEmbedded metadata to build Linux Distributions
	<openembedded-devel@lists.openembedded.org>
Subject: Re: site/* Common site files
Date: Sat, 14 Oct 2006 15:34:34 +0300	[thread overview]
Message-ID: <687683143.20061014153434@gmail.com> (raw)
In-Reply-To: <20061010221107.GB20799@twibble.org>

Hello Jamie,

Wednesday, October 11, 2006, 1:11:07 AM, you wrote:

> 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.


  I can second that Jamie's site/* and config_info work would very
useful for anyone adding a new target to OE. We just went thru some
implementation details of it (I started this off list to not protract
the merge with ungrounded concerns), and once again see that the
framework Jamie put together is very flexible and ready to cover broad
usecases (for example, site files can be overriden down to a package
level (keyword: if needed)).


  So, please count my voice for near-term merge.




-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




  reply	other threads:[~2006-10-14 12:41 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
2006-10-14 12:34     ` Paul Sokolovsky [this message]
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=687683143.20061014153434@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=lenehan@twibble.org \
    --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.