From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] [meta-oe] giflib: Move to OE-Core
Date: Thu, 22 Mar 2012 10:45:17 +0100 [thread overview]
Message-ID: <20120322104517.0600295f@eb-e6520> (raw)
In-Reply-To: <jkes69$nt2$1@dough.gmane.org>
Le Thu, 22 Mar 2012 10:42:33 +0100,
Koen Kooi <koen@dominion.thruhere.net> a écrit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Op 22-03-12 10:40, Eric Bénard schreef:
> > Le Thu, 22 Mar 2012 10:35:31 +0100, Samuel Stirtzel
> > <s.stirtzel@googlemail.com> a écrit :
> >> 2012/3/22 Martin Jansa <martin.jansa@gmail.com>:
> >>> why not add meta-oe dependency to meta-kde/README?
> >>
> >> It is already listed as dependency [1]. But somehow it seems like that
> >> there are users, interested in testing this layer, with an use case
> >> which excludes the meta-oe layer.
> >>
> >>
> > can you describe this use case so that meta-oe gets a chance to adapt.
> >
> > One problem I can see with meta-oe is the fact that it makes changes to
> > the oe-core toolchain : that would be great to put all the toolchain
> > changes in a meta-toolchain (but I think that's what is scheduled with
> > meta-linaro).
>
> In the mean time I bet Khem would love to have people sending patches to
> move the toolchain bits to a meta-toolchain layer inside the
> meta-openembedded repo.
>
ok so expect patches by this weekend for this point.
Eric
next prev parent reply other threads:[~2012-03-22 9:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 14:17 [PATCH] [meta-oe] giflib: Move to OE-Core Samuel Stirtzel
2012-03-21 14:21 ` Samuel Stirtzel
2012-03-21 21:09 ` Koen Kooi
2012-03-22 9:24 ` Samuel Stirtzel
2012-03-22 9:28 ` Martin Jansa
2012-03-22 9:35 ` Samuel Stirtzel
2012-03-22 9:40 ` Eric Bénard
2012-03-22 9:42 ` Koen Kooi
2012-03-22 9:45 ` Eric Bénard [this message]
2012-03-22 10:02 ` Koen Kooi
2012-03-22 16:04 ` Khem Raj
2012-03-22 10:12 ` Samuel Stirtzel
2012-03-22 11:28 ` Koen Kooi
2012-03-22 11:38 ` Samuel Stirtzel
2012-03-22 12:10 ` Koen Kooi
2012-03-22 12:36 ` Samuel Stirtzel
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=20120322104517.0600295f@eb-e6520 \
--to=eric@eukrea.com \
--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