From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] remove gnome-vfs completely
Date: Tue, 27 Sep 2011 17:19:04 +0100 [thread overview]
Message-ID: <1317140351.26109.166.camel@ted> (raw)
In-Reply-To: <201109271516.15542.paul.eggleton@linux.intel.com>
On Tue, 2011-09-27 at 15:16 +0100, Paul Eggleton wrote:
> On Tuesday 27 September 2011 15:02:24 Zhai, Edwin wrote:
> > BTW,
> > I found many recipes in meta-demoapps are not maintained: no
> > LIC_FILES_CHKSUM/SRCREV, no workable SRC_URI, and even no layer.conf under
> > meta-demoapps.
> >
> > We need more test for demoapps, and require each commit to take care of
> > them, or else remove them completely...
>
> My personal opinion as far as OE-core is concerned is that the whole of meta-
> demoapps should be removed; perhaps the recipes within it can be provided in
> another layer (which we can then use within the Yocto project if desired) but
> they do not belong in OE-core IMHO.
I agree it needs to become a separately layer and some of the components
there might be better in other locations.
Its something we meant to deal with later in the OE-Core development
cycle and basically forgot. Maybe someone could file an enhancement
bug? :)
First step would be to move it whole to its own layer repo.
Cheers,
Richard
next prev parent reply other threads:[~2011-09-27 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 13:49 [PATCH 0/1] remove gnome-vfs completely edwin.zhai
2011-09-27 13:49 ` [PATCH 1/1] gnome-vfs: remove this obsolete recipe completely in favor of GIO/GVFS edwin.zhai
2011-09-27 14:56 ` Saul Wold
2011-09-27 14:02 ` [PATCH 0/1] remove gnome-vfs completely Zhai, Edwin
2011-09-27 14:16 ` Paul Eggleton
2011-09-27 16:19 ` Richard Purdie [this message]
2011-09-27 16:56 ` Otavio Salvador
2011-09-27 17:00 ` Paul Eggleton
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=1317140351.26109.166.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.