From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Martin Jansa <martin.jansa@gmail.com>
Subject: Re: [PATCH] Improve handling of 'all' architecture recipes and their interaction with sstate
Date: Tue, 04 Oct 2011 23:00:01 +0100 [thread overview]
Message-ID: <1317765609.14671.118.camel@ted> (raw)
In-Reply-To: <CAP9ODKqb8RGLi_5-_+uegLmtZ7Wo-70oDJcF_R6yaSJ2q9mGwg@mail.gmail.com>
On Sat, 2011-10-01 at 15:48 -0300, Otavio Salvador wrote:
> On Fri, Sep 30, 2011 at 14:09, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> ...
> > Thanks. I've taken the two patches. I'd love to get rid of hal, in fact
> > its on my list of things that need to migrate out of OE-Core...
> ...
>
> From default images this shouldn't be difficult but don't remove hal
> from oe-core since many embedded OS still use it and haven't migrate
> to udev or devicekit yet.
Really? hal doesn't really replace udev though, we can just use udev
directly in place of it for many things now?
Specifically which applications are people using with dependencies on
hal? As has been pointed out we can fix the xserver and that appears to
be the only thing remaining in OE-Core?
Cheers,
Richard
next prev parent reply other threads:[~2011-10-04 22:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 8:19 [PATCH] Improve handling of 'all' architecture recipes and their interaction with sstate Martin Jansa
2011-09-30 14:15 ` Richard Purdie
2011-09-30 16:46 ` Martin Jansa
2011-09-30 17:09 ` Richard Purdie
2011-09-30 17:12 ` Martin Jansa
2011-10-01 18:48 ` Otavio Salvador
2011-10-04 22:00 ` Richard Purdie [this message]
2011-10-04 22:18 ` Koen Kooi
2011-10-05 12:10 ` Otavio Salvador
2011-10-05 12:22 ` Koen Kooi
2011-10-05 12:27 ` Otavio Salvador
2011-10-05 12:29 ` Koen Kooi
2011-10-05 12:34 ` Martin Jansa
2011-10-05 13:02 ` Richard Purdie
2011-10-05 19:32 ` Khem Raj
2011-10-01 18:46 ` Otavio Salvador
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=1317765609.14671.118.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@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