From: "Zhai, Edwin" <edwin.zhai@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/3] webkit-gtk: recommends glib-networking to access https web page
Date: Tue, 28 Jun 2011 16:13:53 +0800 [thread overview]
Message-ID: <4E098D41.4060808@intel.com> (raw)
In-Reply-To: <E91A85C8-4484-4C15-A75D-3A87EB475B4F@dominion.thruhere.net>
Koen Kooi wrote:
>
> Op 28 jun 2011, om 09:42 heeft edwin.zhai@intel.com het volgende
> geschreven:
>
> > From: Zhai Edwin <edwin.zhai@intel.com>
> >
> > [YOCTO #1037] got fixed
> >
> > Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
> > ---
> > meta/recipes-sato/webkit/webkit-gtk_svn.bb | 3 +++
> > 1 files changed, 3 insertions(+), 0 deletions(-)
> >
> > diff --git a/meta/recipes-sato/webkit/webkit-gtk_svn.bb
> b/meta/recipes-sato/webkit/webkit-gtk_svn.bb
> > index 6d134ad..c9ded4e 100644
> > --- a/meta/recipes-sato/webkit/webkit-gtk_svn.bb
> > +++ b/meta/recipes-sato/webkit/webkit-gtk_svn.bb
> > @@ -10,6 +10,9 @@ LIC_FILES_CHKSUM =
> "file://WebCore/rendering/RenderApplet.h;endline=22;md5=fb969
> > DEPENDS = "enchant gnome-keyring libsoup-2.4 curl icu libxml2 cairo
> libxslt libxt libidn gnutls gtk+ gstreamer gst-plugins-base
> flex-native gperf-native perl-native-runtime sqlite3"
>
> > DEPENDS_darwin8 = "curl icu libxml2 cairo libxslt libidn gnutls gtk+
> gstreamer flex-native gperf-native perl-native-runtime sqlite3"
>
> >
> > +# To access ssl web pages
> > +RRECOMMENDS_${PN} += "glib-networking"
>
> Since webkit uses soup and curl, wouldn't it be better to add the
> RRECOMMENDS to soup instead? Webkit knows nothing about GIO.
>
I have considered it. But the drawback is that many other recipes depend
on libsoup, so glib-networking will be built unnecessarily(webkit-gtk is
not in core-image-sato). glib-netwoking just provides some plug-in style
modules, so I think RRECOMMENDS from webkit-gtk should be okay( not
RDEPENDS).
In future, other recipes besides webkit-gtk may ask for glib-networking,
maybe we can change it that time?
What's your opinion?
> regards,
>
> Koen
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2011-06-28 8:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 7:42 [PATCH 0/3] Enable https pages for web brower, v2 edwin.zhai
2011-06-28 7:42 ` [PATCH 1/3] glib-networking: Add 2.28.7 as new recipe edwin.zhai
2011-06-28 9:11 ` Phil Blundell
2011-06-28 9:19 ` Koen Kooi
2011-06-28 12:05 ` Zhai, Edwin
2011-06-28 12:28 ` Koen Kooi
2011-06-28 13:54 ` Richard Purdie
2011-06-29 1:24 ` Zhai, Edwin
2011-06-29 21:13 ` Saul Wold
2011-06-29 21:20 ` Koen Kooi
2011-06-28 7:42 ` [PATCH 2/3] webkit-gtk: recommends glib-networking to access https web page edwin.zhai
2011-06-28 8:01 ` Koen Kooi
2011-06-28 8:13 ` Zhai, Edwin [this message]
2011-06-28 8:36 ` Koen Kooi
2011-06-28 12:08 ` Zhai, Edwin
2011-06-28 12:37 ` Richard Purdie
2011-06-29 1:18 ` Zhai, Edwin
2011-06-28 12:42 ` Zhai, Edwin
2011-06-28 7:42 ` [PATCH 3/3] distro-tracking: Update manual check date for puzzles, gpgme, x11vnc edwin.zhai
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=4E098D41.4060808@intel.com \
--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