From: Phil Blundell <pb@pbcl.net>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/5] nss: add version 3.15.1
Date: Thu, 11 Jul 2013 11:45:30 +0100 [thread overview]
Message-ID: <1373539530.2389.320.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <CAJTo0LbGRLcbb_9J1AdDM1ZFX18SYQi_h6VPwxN3SESDdnN0gA@mail.gmail.com>
On Thu, 2013-07-11 at 11:41 +0100, Burton, Ross wrote:
> On 11 July 2013 11:40, Burton, Ross <ross.burton@intel.com> wrote:
> > On 10 July 2013 09:03, Hongxu Jia <hongxu.jia@windriver.com> wrote:
> >> Network Security Services (NSS) is a set of libraries designed to support
> >> cross-platform development of security-enabled client and server applications.
> >> Applications built with NSS can support SSL v2 and v3, TLS, PKCS 5, PKCS 7,
> >> PKCS 11, PKCS 12, S/MIME, X.509 v3 certificates, and other security standards.
> >
> > What's the rationale for putting this into oe-core instead of updating
> > the recipe in meta-browser?
>
> Of course if I actually read the other mails I'd see it was for LSB.
I think you could still legitimately question whether having recipes in
oe-core that are "just for LSB" is sensible and/or desirable, not least
because dangling libraries that don't have any users are hard to test.
p.
next prev parent reply other threads:[~2013-07-11 10:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 8:03 [PATCH V2 0/5] add nss for LSB library check Hongxu Jia
2013-07-10 8:03 ` [PATCH 1/5] nspr: add native version Hongxu Jia
2013-07-10 8:03 ` [PATCH 2/5] packagegroup-core-lsb: add nss for LSB library check Hongxu Jia
2013-07-10 8:03 ` [PATCH 3/5] nss: add version 3.15.1 Hongxu Jia
2013-07-11 10:40 ` Burton, Ross
2013-07-11 10:41 ` Burton, Ross
2013-07-11 10:45 ` Phil Blundell [this message]
2013-07-11 11:14 ` Burton, Ross
2013-07-11 11:27 ` Hongxu Jia
2013-07-11 11:34 ` Phil Blundell
2013-07-11 13:41 ` Burton, Ross
2013-07-10 8:03 ` [PATCH 4/5] nss: create checksum files for the nss libraries Hongxu Jia
2013-07-12 12:39 ` Burton, Ross
2013-07-12 12:45 ` Hongxu Jia
2013-07-10 8:03 ` [PATCH 5/5] nss: fix incorrect shebang line of perl script Hongxu Jia
2013-07-11 8:39 ` Trevor Woerner
2013-07-11 8:58 ` Hongxu Jia
2013-07-11 9:23 ` Paul Eggleton
2013-07-11 9:28 ` Hongxu Jia
2013-07-11 12:04 ` [PATCH V3 0/5] add nss for LSB library check (cover letter only) Hongxu Jia
-- strict thread matches above, loose matches on Subject: below --
2013-07-09 12:30 [PATCH 0/5]add nss for LSB library check Hongxu Jia
2013-07-09 12:30 ` [PATCH 3/5] nss: add version 3.15.1 Hongxu Jia
2013-07-09 12:44 ` Paul Eggleton
2013-07-09 13:29 ` Hongxu Jia
2013-07-09 13:38 ` Paul Eggleton
2013-07-09 13:41 ` Khem Raj
2013-07-10 1:26 ` Hongxu Jia
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=1373539530.2389.320.camel@phil-desktop.brightsign \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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