From: "Zhai, Edwin" <edwin.zhai@intel.com>
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 22:02:24 +0800 [thread overview]
Message-ID: <20110927140224.GA10415@edwin-gen> (raw)
In-Reply-To: <cover.1317131040.git.edwin.zhai@intel.com>
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...
On Tue, Sep 27, 2011 at 09:49:25PM +0800, edwin.zhai@intel.com wrote:
> From: Zhai Edwin <edwin.zhai@intel.com>
>
> All,
> This patch remove gnome-vfs completely: remove itself, dependence on it, and
> other obsolete recipe depending on it.
>
> Last time, I remember one recipe in oe-core depends on gnome-vfs, but nobody
> depends on it. Could somebody have a double check on oe-core?
>
> Thanks,
> Edwin
>
> The following changes since commit e3c5d7a90ae179af0ac128ea4dfc1a5a6602c2e4:
>
> libtool: Fix an issue where unnecessary rpaths were being injected (2011-09-26 17:56:44 +0100)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib gzhai/master2
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=gzhai/master2
>
> Zhai Edwin (1):
> gnome-vfs: remove this obsolete recipe completely in favor of
> GIO/GVFS
>
> .../recipes-gnome/libgsf/libgsf_1.14.5.bb | 8 ++-
> meta-demoapps/recipes-graphics/clutter/table.inc | 13 -----
> .../recipes-graphics/clutter/table/fixes.patch | 16 ------
> .../recipes-graphics/clutter/table_git.bb | 15 ------
> .../conf/distro/include/distro_tracking_fields.inc | 11 ----
> meta/conf/multilib.conf | 1 -
> .../gnome/gnome-vfs-2.24.4/gconftool-lossage.patch | 13 -----
> .../gnome-vfs-2.24.4/gnome-vfs-no-kerberos.patch | 53 --------------------
> meta/recipes-gnome/gnome/gnome-vfs_2.24.4.bb | 50 ------------------
> meta/recipes-kernel/oprofile/oprofileui.inc | 2 +-
> 10 files changed, 7 insertions(+), 175 deletions(-)
> delete mode 100644 meta-demoapps/recipes-graphics/clutter/table.inc
> delete mode 100644 meta-demoapps/recipes-graphics/clutter/table/fixes.patch
> delete mode 100644 meta-demoapps/recipes-graphics/clutter/table_git.bb
> delete mode 100644 meta/recipes-gnome/gnome/gnome-vfs-2.24.4/gconftool-lossage.patch
> delete mode 100644 meta/recipes-gnome/gnome/gnome-vfs-2.24.4/gnome-vfs-no-kerberos.patch
> delete mode 100644 meta/recipes-gnome/gnome/gnome-vfs_2.24.4.bb
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
best rgds,
edwin
next prev parent reply other threads:[~2011-09-27 14:09 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 ` Zhai, Edwin [this message]
2011-09-27 14:16 ` [PATCH 0/1] remove gnome-vfs completely Paul Eggleton
2011-09-27 16:19 ` Richard Purdie
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=20110927140224.GA10415@edwin-gen \
--to=edwin.zhai@intel.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