From: Xiaofeng Yan <xiaofeng.yan@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] pango.inc: add directory "/etc/pango"
Date: Fri, 13 Jan 2012 15:05:41 +0800 [thread overview]
Message-ID: <4F0FD7C5.4040907@windriver.com> (raw)
In-Reply-To: <1326400424.3360.1.camel@lenovo.internal.reciva.com>
On 2012年01月13日 04:33, Phil Blundell wrote:
> On Thu, 2012-01-12 at 12:30 -0800, Saul Wold wrote:
>> On 01/12/2012 12:12 AM, Xiaofeng Yan wrote:
>>> -FILES_${PN} = "/etc/pango/* ${bindir}/* ${libdir}/libpango*${SOLIBS}"
>>> +FILES_${PN} += "${syscondir}/* ${bindir}/* ${libdir}/libpango*${SOLIBS}"
>> Is this too general? Should it be ${sysconfdir}/pango?
> "${sysconfdir}" is in the default FILES_${PN} anyway.
I will remove this changes.
> (Also,
> "${syscondir}/*" won't match anything since there is no such variable.)
>
> So this change is largely benign but it won't accomplish much.
>
> p.
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2012-01-13 7:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 8:12 PATCH 0/3] Fix the error when building image "core-image-gtk-directfb" Xiaofeng Yan
2012-01-12 8:12 ` [PATCH 1/3] gtk.inc: Change configuration of directfb to gtk-directfb Xiaofeng Yan
2012-01-12 8:12 ` [PATCH 2/3] cairo.inc: " Xiaofeng Yan
2012-01-12 8:12 ` [PATCH 3/3] pango.inc: add directory "/etc/pango" Xiaofeng Yan
2012-01-12 20:30 ` Saul Wold
2012-01-12 20:33 ` Phil Blundell
2012-01-13 7:05 ` Xiaofeng Yan [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-13 7:06 [PATCH 0/3]: Fix the error when building image "core-image-gtk-directfb" Xiaofeng Yan
2012-01-13 7:06 ` [PATCH 3/3] pango.inc: add directory "/etc/pango" Xiaofeng Yan
2012-01-16 4:34 ` Saul Wold
2012-01-17 9:11 ` Khem Raj
2012-01-17 10:13 ` Koen Kooi
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=4F0FD7C5.4040907@windriver.com \
--to=xiaofeng.yan@windriver.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 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.