From: Richard Purdie <rpurdie@rpsys.net>
To: Using the OpenEmbedded metadata to build Linux Distributions
<openembedded-devel@openembedded.org>
Subject: Re: site/* - using common files for site information
Date: Fri, 25 Aug 2006 09:08:09 +0100 [thread overview]
Message-ID: <1156493289.5554.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20060825053341.GA29761@twibble.org>
On Fri, 2006-08-25 at 15:33 +1000, Jamie Lenehan wrote:
> On Fri, Aug 18, 2006 at 01:33:12AM +1000, Jamie Lenehan wrote:
> > On Thu, Aug 17, 2006 at 08:53:25PM +1000, Jamie Lenehan wrote:
> > > Attached is a patch I'd like to propose to allow for multiple site
> > > files to be used so that common stuff can be moved into common site
> > [...]
>
> I've extended this a bit to allow site files to be per package,
> rather than having to be global - including version specific site
> files (such as db needs). Lots of packages just need a few site file
> entries which are generally common across all builds or specific to
> glibc or uclibc.
>
> Probably the most useful part is allowing all of the x86 site files
> to be merged together.
>
> If no one has any comments on this then I guess I'll push it in.
> First the info.bbclass, then clean up the few recipes that directly
> mess with CONFIG_SITE, then clean up the x86 files and the the few
> recipes that I've been maintaining.
For what its worth, I like the idea of this but haven't had time to
review the patches. The name info.bbclass is perhaps too generic though
- could you call it something like autotools-info.bbclass?
Regards,
Richard
next prev parent reply other threads:[~2006-08-25 8:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060817105325.GA2172@twibble.org>
[not found] ` <20060817153312.GA23152@twibble.org>
2006-08-25 5:33 ` site/* - using common files for site information Jamie Lenehan
2006-08-25 8:08 ` Richard Purdie [this message]
2006-08-25 8:22 ` Jamie Lenehan
2006-08-25 8:40 ` Richard Purdie
2006-08-25 9:34 ` Jamie Lenehan
2006-08-25 9:57 ` Michael 'Mickey' Lauer
2006-08-28 0:05 ` Jamie Lenehan
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=1156493289.5554.2.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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