From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] xorg-font-common.inc: break runtime dependency loop
Date: Mon, 19 Dec 2011 14:45:20 +0000 [thread overview]
Message-ID: <1324305920.4568.176.camel@ted> (raw)
In-Reply-To: <201112190148.16063.schnitzeltony@gmx.de>
On Mon, 2011-12-19 at 01:48 +0100, Andreas Müller wrote:
> On Sunday, December 18, 2011 02:03:17 AM Andreas Müller wrote:
> > required since opkg update [1]
> >
> Hope there is no need to apply this one. Will test RP's patch tomorrow
To be honest the font-* dependencies look rather wrong to me and in need
of disentangling. I'll hold off this patch and see if we can some up
with something better though.
I suspect the better fix would be to have the actual fonts have a
separate.inc with the dependencies so encodings/utils/alias don't get
those defaults...
Cheers,
Richard
prev parent reply other threads:[~2011-12-19 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 1:03 [PATCH] xorg-font-common.inc: break runtime dependency loop Andreas Müller
2011-12-18 9:20 ` Koen Kooi
2011-12-19 0:48 ` Andreas Müller
2011-12-19 14:45 ` Richard Purdie [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=1324305920.4568.176.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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