Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Christopher Larson <kergoth@gmail.com>
Cc: Christopher Larson <chris_larson@mentor.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv3 0/2] Add ca-certificates recipe
Date: Wed, 28 Aug 2013 10:19:08 +0200	[thread overview]
Message-ID: <20130828081908.GF3544@jama> (raw)
In-Reply-To: <cover.1377285913.git.chris_larson@mentor.com>

[-- Attachment #1: Type: text/plain, Size: 2044 bytes --]

On Fri, Aug 23, 2013 at 12:26:13PM -0700, Christopher Larson wrote:
> From: Christopher Larson <chris_larson@mentor.com>
> 
> This is based on the meta-oe recipe, with enhancements, and prepopulates the
> certificates for the nativesdk version, for later use in the
> buildtools-tarball.
> 
> The following changes since commit 9b05c65450526522d7358d0c0901b594de546748:
> 
>   sstate: Fix the relative symlink replacement code (2013-08-23 16:59:04 +0100)
> 
> are available in the git repository at:
> 
>   https://github.com/kergoth/oe-core.git ca-certificates
> 
> Christopher Larson (2):
>   ca-certificates: add recipe (version 20130610)
>   nativesdk-ca-certificates: prepopulate ca-certificates.crt

Are you going to send patches to oe-devel to remove moved 
recipes/bbclasses ?

> 
>  ...01-update-ca-certificates-remove-c-rehash.patch | 46 +++++++++++++++
>  .../0002-update-ca-certificates-use-SYSROOT.patch  | 55 +++++++++++++++++
>  .../ca-certificates/default-sysroot.patch          | 55 +++++++++++++++++
>  .../ca-certificates/ca-certificates/sbindir.patch  | 20 +++++++
>  .../ca-certificates/ca-certificates_20130610.bb    | 69 ++++++++++++++++++++++
>  5 files changed, 245 insertions(+)
>  create mode 100644 meta/recipes-support/ca-certificates/ca-certificates/0001-update-ca-certificates-remove-c-rehash.patch
>  create mode 100644 meta/recipes-support/ca-certificates/ca-certificates/0002-update-ca-certificates-use-SYSROOT.patch
>  create mode 100644 meta/recipes-support/ca-certificates/ca-certificates/default-sysroot.patch
>  create mode 100644 meta/recipes-support/ca-certificates/ca-certificates/sbindir.patch
>  create mode 100644 meta/recipes-support/ca-certificates/ca-certificates_20130610.bb
> 
> -- 
> 1.8.3.4
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  parent reply	other threads:[~2013-08-28  8:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23 19:26 [PATCHv3 0/2] Add ca-certificates recipe Christopher Larson
2013-08-23 19:26 ` [PATCHv3 1/2] ca-certificates: add recipe (version 20130610) Christopher Larson
2013-08-23 19:26 ` [PATCHv3 2/2] nativesdk-ca-certificates: prepopulate ca-certificates.crt Christopher Larson
2013-08-28  8:19 ` Martin Jansa [this message]
2013-08-28 12:31   ` [PATCHv3 0/2] Add ca-certificates recipe Paul Eggleton
2013-08-28 13:30     ` Chris Larson

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=20130828081908.GF3544@jama \
    --to=martin.jansa@gmail.com \
    --cc=chris_larson@mentor.com \
    --cc=kergoth@gmail.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