All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] package.bbclass: Let pn be eglibc for eglibc-locale
Date: Thu, 26 Jul 2012 21:38:05 +0100	[thread overview]
Message-ID: <1343335085.9574.32.camel@ted> (raw)
In-Reply-To: <CAMKF1so+OJTjN+fRP8DJK2zCNKUyTFYJ==zUMkRm1+-6FkYCvg@mail.gmail.com>

On Thu, 2012-07-26 at 13:16 -0700, Khem Raj wrote:
> On Thu, Jul 26, 2012 at 11:58 AM, Phil Blundell <philb@gnu.org> wrote:
> >
> > Bletch!  There must surely be some way to solve this problem without
> > hacking recipe names into package.bbclass.
> 
> Yes making eglibc-locale base package to be non empty. So if we put in
> something there that it never turns out to be empty is one way

Well, having things depending on eglibc-locale-locale is wrong in many
ways :/. eglibc is just the only package we split the locale generation
into a separate recipe for.

A more generic check in there which would work for multiple libcs would
be:

if pn.endswith("-locale"):
    pn = pn[:-7]

the other alternative which comes to mind would be so set a variable
with the name we want used there, defaulting it to PN.

Cheers,

Richard




  reply	other threads:[~2012-07-26 20:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 18:49 [PATCH] package.bbclass: Let pn be eglibc for eglibc-locale Saul Wold
2012-07-26 18:58 ` Phil Blundell
2012-07-26 20:16   ` Khem Raj
2012-07-26 20:38     ` Richard Purdie [this message]
2012-07-26 20:52       ` Mark Hatle
2012-07-26 20:53       ` Phil Blundell
2012-07-26 21:27         ` Khem Raj
2012-07-26 21:47           ` Mark Hatle
2012-07-29 20:22             ` Khem Raj
2012-07-29 20:34               ` Khem Raj

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=1343335085.9574.32.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 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.