From: Ulf Samuelsson <ulf_samuelsson@telia.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe] tz*: download location has moved
Date: Wed, 14 Dec 2011 00:14:23 +0100 [thread overview]
Message-ID: <4EE7DC4F.4070703@telia.com> (raw)
In-Reply-To: <CAMKF1soZMLXz2_0OU9-4HmEyYDK-h40=940cCTqf8O53AkR7-Q@mail.gmail.com>
On 2011-12-13 21:15, Khem Raj wrote:
> On Tue, Dec 13, 2011 at 11:38 AM, Saul Wold<sgw@linux.intel.com> wrote:
>> On 12/13/2011 07:11 AM, ulf@emagii.com wrote:
>>> From: Ulf Samuelsson<ulf@emagii.com>
>>>
>>> Signed-off-by: Ulf Samuelsson<ulf@emagii.com>
>>> ---
>>> meta-oe/recipes-extended/tzcode/tzcode-native.inc | 6 +++---
>>> meta-oe/recipes-extended/tzdata/tzdata.inc | 4 ++--
>>> 2 files changed, 5 insertions(+), 5 deletions(-)
>>>
>> This was fixed in oe-core, What's the reason that a tz* set is needed in
>> meta-oe? Can we remove them from meta-oe or is the older version needed by
>> someone?
>>
> there are some differences e.g. met-oe it installs a sane default for timezone
> may be if those differences can be merged then it would make it go away
>
> -Khem
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Angstrom has meta-openembedded/meta-oe before openembedded-core in the
layer list,
so this is needed to build Angstrom.
A merged recipe would be better of course.
--
Best Regards
Ulf Samuelsson
prev parent reply other threads:[~2011-12-13 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 15:11 [meta-oe] tz*: download location has moved ulf
2011-12-13 19:38 ` Saul Wold
2011-12-13 20:15 ` Khem Raj
2011-12-13 23:14 ` Ulf Samuelsson [this message]
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=4EE7DC4F.4070703@telia.com \
--to=ulf_samuelsson@telia.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 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.