From: "Zhai, Edwin" <edwin.zhai@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] glib-networking: Add 2.28.7 as new recipe
Date: Tue, 28 Jun 2011 09:02:40 +0800 [thread overview]
Message-ID: <4E092830.8050002@intel.com> (raw)
In-Reply-To: <F8790096-AFE8-4CDA-B025-CE8359FC48BF@dominion.thruhere.net>
Koen Kooi wrote:
>
> Op 25 jun 2011, om 05:54 heeft edwin.zhai@intel.com het volgende
> geschreven:
>
> > From: Zhai Edwin <edwin.zhai@intel.com>
> >
> > glib-networking contains the implementations of certain GLib networking
> > features that cannot be implemented directly in GLib itself because
> of their
> > dependencies. TLS/SSL support is one of them, which is needed for
> accessing SSL
> > web page.
> >
> > Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
> > ---
> > meta/recipes-sato/web/glib-networking_2.28.7.bb | 21
> +++++++++++++++++++++
>
> The recipe looks good, but it shouldn't be hidden in recipes-sato/web/
>
From function level, only web requires TLS or proxy support. But in
fact, glib-networking is part of glib. How about recipes-core/, like glib?
> _______________________________________________
> 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 1:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-25 3:54 [PATCH 0/2] Enable https pages for web browser edwin.zhai
2011-06-25 3:54 ` [PATCH 1/2] glib-networking: Add 2.28.7 as new recipe edwin.zhai
2011-06-27 9:53 ` Koen Kooi
2011-06-28 1:02 ` Zhai, Edwin [this message]
2011-06-27 10:17 ` Koen Kooi
2011-06-28 1:20 ` Zhai, Edwin
2011-06-25 3:54 ` [PATCH 2/2] webkit-gtk: recommends glib-networking to access https web page 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=4E092830.8050002@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