Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Revert "kmod: Use base_libdir for installing libkmod"
Date: Thu, 17 May 2012 23:21:51 +0100	[thread overview]
Message-ID: <2622747.VEgA05EEDD@helios> (raw)
In-Reply-To: <CAP9ODKoV-pZTPrn5HrLR5b4soceeN+81e3HWYQ_OxdbVfDiQvg@mail.gmail.com>

On Thursday 17 May 2012 19:11:20 Otavio Salvador wrote:
> On Thu, May 17, 2012 at 7:01 PM, Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
> > On Thursday 17 May 2012 18:51:05 Otavio Salvador wrote:
> >> It is important to state that if OE-Core breaks Meta-OE this is
> >> crticial. It is not Yocto that people use and many active contributors
> >> use Meta-OE so it is important and critical to that people. Seems more
> >> health to the project to give the deserved value to Meta-OE instead of
> >> badmouth it...
> > 
> > The sooner people can start using it without fear of it doing unexpected
> > things, the sooner people will be able to have more confidence in it and
> > stop making negative comments about it. As it stands the way a lot of
> > people treat meta-oe is a source of recipes to be copied elsewhere
> > because they feel they cannot use the layer as a whole. I think that's a
> > big shame.
> 
> Agreed; the nice thing about Free Software is that we can do something
> about it; do negative comments help nothing.
> 
> Most people on Yocto do not contribute actively to Meta-OE. As
> example, you did 12 commits in total to it...

No, we don't, but that's probably because we have our hands full maintaining 
BitBake and OE-Core (with the help of others in the community, of course). Not 
to mention that when we do enable it on top of OE-Core / Poky without wanting 
to use systemd, it makes a whole raft of changes that usually cause breakage 
of some kind because that configuration is rarely tested. This just makes using 
and contributing to meta-oe harder.

We really do recognise that there has to be a source of recipes outside OE-
Core, and meta-oe is the current place for a lot of those. However there is 
just so much work to be done on BitBake and OE-Core that venturing into meta-
oe as well is something a lot of us don't have time for in our daily work, 
especially with its current state. I do use meta-oe when I'm building stuff at 
home but there I more or less have my hands full maintaining meta-handheld, 
meta-opie and a bunch of other things.

I hope during the current development cycle that I will have time to 
contribute to meta-oe further. I can't make any promises though.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-05-17 22:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15  9:32 [PATCH] Revert "kmod: Use base_libdir for installing libkmod" Koen Kooi
2012-05-15 20:54 ` Khem Raj
2012-05-17 20:29   ` Richard Purdie
2012-05-17 20:44     ` Koen Kooi
2012-05-17 21:02       ` Richard Purdie
2012-05-17 21:16         ` Tom Rini
2012-05-17 21:25           ` Paul Eggleton
2012-05-17 21:51             ` Otavio Salvador
2012-05-17 22:01               ` Paul Eggleton
2012-05-17 22:11                 ` Otavio Salvador
2012-05-17 22:21                   ` Paul Eggleton [this message]
2012-05-17 22:22               ` Phil Blundell
2012-05-17 22:50               ` Khem Raj
2012-05-17 23:00                 ` Andreas Müller
2012-05-18  6:19         ` Koen Kooi
2012-05-18  8:16           ` Koen Kooi
2012-05-18  7:52         ` Koen Kooi
2012-05-18 10:29           ` Richard Purdie
2012-05-18 10:37             ` Koen Kooi

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=2622747.VEgA05EEDD@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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