Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
Subject: Re: should recipes be distro agnostic?
Date: Thu, 26 Jan 2012 11:31:21 +0000	[thread overview]
Message-ID: <1494171.ziDK2I0A7F@helios> (raw)
In-Reply-To: <CACW_hTb9UZACKZ+acn2jp-PZzrk1YkbmohyFxoi2deJdRvJpKw@mail.gmail.com>

On Thursday 26 January 2012 07:52:22 Frans Meulenbroeks wrote:
> By coincidence I bumped into this in oe-core:
> 
> ./meta/recipes-devtools/apt/apt.inc:EXTRA_OECONF_append_angstrom = "
> ac_cv_glibc_ver=libc6.4"
> 
> That also triggered me to do this:
> 
> frans@frans-desktop:~/workspace/openembedded-core$ grep -r _poky .
> ./meta/recipes-sato/pcmanfm/pcmanfm_0.9.10.bb:DEPENDS_append_poky = "
> libowl"
> ./meta/recipes-sato/pcmanfm/pcmanfm_0.9.10.bb:SRC_URI_append_poky = "
> file://owl-window-menu.patch"
> ./meta/recipes-sato/leafpad/leafpad_0.8.18.1.bb:DEPENDS_append_poky = "
> libowl"
> ./meta/recipes-sato/leafpad/leafpad_0.8.18.1.bb:SRC_URI_append_poky += "
> file://owl-menu.patch;apply=yes "
> ./meta/recipes-sato/pimlico/dates.inc:OWL_poky = "--enable-owl
> --disable-dnd"
> ./meta/recipes-sato/pimlico/dates.inc:DEPENDS_append_poky = " libowl"
> ./meta/recipes-sato/pimlico/dates.inc:SRC_URI_append_poky = "
> file://dates-owl-window-menu.patch;apply=yes "
> ./meta/recipes-sato/pimlico/tasks_0.19.bb:OWL_poky = "--with-owl"
> ./meta/recipes-sato/pimlico/contacts.inc:DEPENDS_append_poky = " libowl"
> ./meta/recipes-sato/pimlico/contacts.inc:OWL_poky = "--enable-owl"
> ./meta/recipes-sato/pimlico/contacts.inc:SRC_URI_append_poky = "
> file://contacts-owl-window-menu.patch;apply=yes "
> ./meta/recipes-sato/pimlico/tasks.inc:DEPENDS_append_poky = " libowl"
> ./meta/recipes-sato/pimlico/tasks.inc:OWL_poky ?= "--enable-owl"
> ./meta/recipes-sato/puzzles/oh-puzzles_git.bb:DEPENDS_append_poky = "
> libowl"
> ./meta/recipes-sato/puzzles/oh-puzzles_git.bb:SRC_URI_append_poky = "
> file://oh-puzzles-owl-menu.patch;striplevel=0 "
> ./meta/recipes-devtools/gcc/gcc-runtime_4.6.bb:EXTRA_OECONF_append_poky-lsb
> = " --enable-clocale=gnu"
> 
> I'd hoped oe-core to be core and not know things about distro's etc.
> E.g. the first case with apt, this should probably be fixed with a
> .bbappend in the angstrom layer, shouldn't it.
> And the poky things in a poky layer.

Absolutely, there should be no distro-specific items in OE-Core at all, and I 
have to admit I was not aware they were there. Most of the poky ones seem to 
be related to enabling libowl in various Sato apps - I don't know enough about 
this area to know if we should now just always be applying these or whether 
they indeed need to be moved out. Richard/Saul/anyone else?

Regarding meta-oe, I think we have bigger issues than the items you found (see 
other thread on OE-devel) although they shouldn't be in there either.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-01-26 11:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26  6:52 should recipes be distro agnostic? Frans Meulenbroeks
2012-01-26 11:31 ` Paul Eggleton [this message]
2012-01-26 11:38   ` 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=1494171.ziDK2I0A7F@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=fransmeulenbroeks@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox