All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
	openembedded-devel@lists.openembedded.org
Subject: Re: Duplicate recipes in meta-oe
Date: Mon, 06 Feb 2012 15:39:24 +0000	[thread overview]
Message-ID: <1408084.uBj8QddilE@helios> (raw)
In-Reply-To: <CAMKF1soq=EaZ4KMb7McFcEjNyTVT2sMHPHvEr11+kL603iCOUQ@mail.gmail.com>

On Saturday 04 February 2012 10:19:38 Khem Raj wrote:
> recipes-devtools/python/python-setuptools_0.6c11.bb
> 
> one in meta-oe has
> NATIVE_INSTALL_WORKS = "1"
> I dont know if this is needed anymore if not then this can be delete
> from meta-oe

NATIVE_INSTALL_WORKS is no longer needed for OE-Core, so this can go.
 
> recipes-extended/tzcode/tzcode-native_2011i.bb
> 
> We are good with one for oe-core I think Andrea is working on it.

I talked to Koen at FOSDEM and apparently he prefers having a symlink rather 
than a copy for the timezone file. I can't express an opinion one way or 
another but it sounds like this one aspect still needs to be resolved - should 
this be selectable?
 
Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



WARNING: multiple messages have this Message-ID (diff)
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
	openembedded-devel@lists.openembedded.org
Subject: Re: [OE-core] Duplicate recipes in meta-oe
Date: Mon, 06 Feb 2012 15:39:24 +0000	[thread overview]
Message-ID: <1408084.uBj8QddilE@helios> (raw)
In-Reply-To: <CAMKF1soq=EaZ4KMb7McFcEjNyTVT2sMHPHvEr11+kL603iCOUQ@mail.gmail.com>

On Saturday 04 February 2012 10:19:38 Khem Raj wrote:
> recipes-devtools/python/python-setuptools_0.6c11.bb
> 
> one in meta-oe has
> NATIVE_INSTALL_WORKS = "1"
> I dont know if this is needed anymore if not then this can be delete
> from meta-oe

NATIVE_INSTALL_WORKS is no longer needed for OE-Core, so this can go.
 
> recipes-extended/tzcode/tzcode-native_2011i.bb
> 
> We are good with one for oe-core I think Andrea is working on it.

I talked to Koen at FOSDEM and apparently he prefers having a symlink rather 
than a copy for the timezone file. I can't express an opinion one way or 
another but it sounds like this one aspect still needs to be resolved - should 
this be selectable?
 
Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-02-06 15:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04 17:12 Duplicate recipes in meta-oe Khem Raj
2012-02-04 18:19 ` Khem Raj
2012-02-06 15:39   ` Paul Eggleton [this message]
2012-02-06 15:39     ` [OE-core] " Paul Eggleton
2012-02-06 15:47     ` [oe] " Otavio Salvador
2012-02-06 15:47       ` [OE-core] " Otavio Salvador
2012-02-06 15:55     ` Phil Blundell
2012-02-06 16:07       ` Koen Kooi
2012-02-06 19:43       ` Philip Balister
2012-02-06 20:02         ` Mark Hatle
2012-02-06 20:20         ` Phil Blundell
2012-02-06 20:48           ` Mark Hatle
2012-02-06 22:35             ` Phil Blundell
2012-02-06 23:38               ` Mark Hatle
2012-02-06 22:59           ` 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=1408084.uBj8QddilE@helios \
    --to=paul.eggleton@linux.intel.com \
    --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.