All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-core@lists.openembedded.org,
	openembedded-devel@lists.openembedded.org
Subject: Re: Heads up: _remove in recipe namespace - check your layers
Date: Mon, 02 Sep 2013 17:41:38 -0400	[thread overview]
Message-ID: <20130902214138.GA30776@denix.org> (raw)
In-Reply-To: <5772089.rktQrocuuR@helios>

On Mon, Sep 02, 2013 at 10:54:20AM +0100, Paul Eggleton wrote:
> Hi all,
> 
> With the recent addition of a _remove operator into BitBake in master [1] any 
> use of _remove_ within a name or _remove at the end of a name within recipe 
> namespace (i.e. function and variable names) needs to be changed to avoid 
> unexpected behaviour. This change is now in master and will be in the upcoming 
> release. Please check the layers you maintain and change any instances of 
> these to avoid the use of _remove. You can use the following command to find 
> these (of course ignoring anything that's not in a recipe, bbclass, inc file 
> etc.):
> 
>   git grep _remove[^a-zA-Z]
> 
> In particular I've checked a number of layers that I have fetched locally, and 
> references exist in meta-arago-distro and meta-angstrom, so these will need to 
> be fixed as soon as possible.

Paul,

Thanks for the heads up! While meta-arago is currently based on Dylan, I've
made the necessary change in my layer so it will be ready for the master.
Thanks.

--
Denys


WARNING: multiple messages have this Message-ID (diff)
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-core@lists.openembedded.org,
	openembedded-devel@lists.openembedded.org
Subject: Re: [OE-core] Heads up: _remove in recipe namespace - check your layers
Date: Mon, 02 Sep 2013 17:41:38 -0400	[thread overview]
Message-ID: <20130902214138.GA30776@denix.org> (raw)
In-Reply-To: <5772089.rktQrocuuR@helios>

On Mon, Sep 02, 2013 at 10:54:20AM +0100, Paul Eggleton wrote:
> Hi all,
> 
> With the recent addition of a _remove operator into BitBake in master [1] any 
> use of _remove_ within a name or _remove at the end of a name within recipe 
> namespace (i.e. function and variable names) needs to be changed to avoid 
> unexpected behaviour. This change is now in master and will be in the upcoming 
> release. Please check the layers you maintain and change any instances of 
> these to avoid the use of _remove. You can use the following command to find 
> these (of course ignoring anything that's not in a recipe, bbclass, inc file 
> etc.):
> 
>   git grep _remove[^a-zA-Z]
> 
> In particular I've checked a number of layers that I have fetched locally, and 
> references exist in meta-arago-distro and meta-angstrom, so these will need to 
> be fixed as soon as possible.

Paul,

Thanks for the heads up! While meta-arago is currently based on Dylan, I've
made the necessary change in my layer so it will be ready for the master.
Thanks.

--
Denys


  parent reply	other threads:[~2013-09-02 21:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02  9:54 Heads up: _remove in recipe namespace - check your layers Paul Eggleton
2013-09-02 21:39 ` Denys Dmytriyenko
2013-09-02 21:41 ` Denys Dmytriyenko [this message]
2013-09-02 21:41   ` [OE-core] " Denys Dmytriyenko

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=20130902214138.GA30776@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@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.