From: Pascal Bach <pascal.bach@siemens.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-webserver][PATCH 2/2] nginx: add stable version 1.8.1 as alternative to the mainline version 1.9.x
Date: Tue, 16 Feb 2016 12:40:45 +0100 [thread overview]
Message-ID: <1455622845-14510-3-git-send-email-pascal.bach@siemens.com> (raw)
In-Reply-To: <1455622845-14510-1-git-send-email-pascal.bach@siemens.com>
The 1.8 branch is the current stable branch of nginx.
This means the branch doesn't get new features, but is still supported with bugfixes.
Depending on the use case it is more suitable to use on an embedded device
than the 1.9 branch which adds new features with every release.
---
meta-webserver/recipes-httpd/nginx/nginx_1.8.1.bb | 4 ++++
1 file changed, 4 insertions(+)
create mode 100644 meta-webserver/recipes-httpd/nginx/nginx_1.8.1.bb
diff --git a/meta-webserver/recipes-httpd/nginx/nginx_1.8.1.bb b/meta-webserver/recipes-httpd/nginx/nginx_1.8.1.bb
new file mode 100644
index 0000000..ec3aef2
--- /dev/null
+++ b/meta-webserver/recipes-httpd/nginx/nginx_1.8.1.bb
@@ -0,0 +1,4 @@
+require nginx.inc
+
+SRC_URI[md5sum] = "2e91695074dbdfbf1bcec0ada9fda462"
+SRC_URI[sha256sum] = "8f4b3c630966c044ec72715754334d1fdf741caa1d5795fb4646c27d09f797b7"
--
2.1.4
next prev parent 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 [meta-webserver][PATCH 0/2] nginx: make mainline and stable version available Pascal Bach
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 ` Pascal Bach [this message]
2016-03-03 9:07 ` [meta-webserver][PATCH 2/2] nginx: add stable version 1.8.1 as alternative to the mainline version 1.9.x 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-3-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