From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: is the virtual package <locale>-tanslation correct?
Date: Tue, 24 Apr 2012 11:48:10 +0100 [thread overview]
Message-ID: <1335264491.27021.66.camel@phil-desktop> (raw)
In-Reply-To: <1335264349.12692.120.camel@ted>
On Tue, 2012-04-24 at 11:45 +0100, Richard Purdie wrote:
> On Tue, 2012-04-24 at 10:42 +0100, Phil Blundell wrote:
> > Yes, that is the intended behaviour. This is necessary to support
> > dynamically installed language packs.
>
> What uses this out of interest?
I'm not entirely sure to be honest. We used to use it quite heavily in
Familiar but I have no idea whether Angstrom does the same. The systems
I'm working on nowadays don't tend to require language packs so I
haven't personally used that mechanism for a while.
p.
next prev parent reply other threads:[~2012-04-24 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 9:33 is the virtual package <locale>-tanslation correct? Lu, Lianhao
2012-04-24 9:42 ` Phil Blundell
2012-04-24 10:45 ` Richard Purdie
2012-04-24 10:48 ` Phil Blundell [this message]
2012-04-24 16:33 ` Richard Purdie
2012-04-24 16:47 ` Phil Blundell
2012-04-24 19:59 ` Richard Purdie
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=1335264491.27021.66.camel@phil-desktop \
--to=philb@gnu.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