From: Pascal Bach <pascal.bach@siemens.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-webserver][PATCH 0/2] nginx: make mainline and stable version available
Date: Tue, 16 Feb 2016 12:40:43 +0100 [thread overview]
Message-ID: <1455622845-14510-1-git-send-email-pascal.bach@siemens.com> (raw)
Nginx has two supported branches, mainline and stable.
Currently meta-webserver contains the mainline version (1.9.x) of nginx.
For embedded system it might however be more appropriate to use the stable version (1.8.x)
which only receives security updates and bugfixes.
This changeset restructures the nginx recipe to provide recipes for both 1.8 and 1.9 branches.
Pascal Bach (2):
nginx: split parts out of the recipe into nginx.inc
nginx: add stable version 1.8.1 as alternative to the mainline version
1.9.x
meta-webserver/recipes-httpd/nginx/nginx.inc | 136 +++++++++++++++++++++
meta-webserver/recipes-httpd/nginx/nginx_1.8.1.bb | 4 +
meta-webserver/recipes-httpd/nginx/nginx_1.9.10.bb | 136 +--------------------
3 files changed, 141 insertions(+), 135 deletions(-)
create mode 100644 meta-webserver/recipes-httpd/nginx/nginx.inc
create mode 100644 meta-webserver/recipes-httpd/nginx/nginx_1.8.1.bb
--
2.1.4
next reply other threads:[~2016-02-16 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 11:40 Pascal Bach [this message]
2016-02-16 11:40 ` [meta-webserver][PATCH 1/2] nginx: split parts out of the recipe into nginx.inc Pascal Bach
2016-02-16 11:40 ` [meta-webserver][PATCH 2/2] nginx: add stable version 1.8.1 as alternative to the mainline version 1.9.x Pascal Bach
2016-03-03 9:07 ` Martin Jansa
2016-02-16 11:51 ` [meta-webserver][PATCH 0/2] nginx: make mainline and stable version available Otavio Salvador
2016-02-17 14:24 ` Pascal Bach
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=1455622845-14510-1-git-send-email-pascal.bach@siemens.com \
--to=pascal.bach@siemens.com \
--cc=openembedded-devel@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