From: Pascal Bach <pascal.bach@siemens.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-webserver][PATCH 0/2] nginx: make mainline and stable version available
Date: Wed, 17 Feb 2016 15:24:48 +0100 [thread overview]
Message-ID: <56C482B0.6020608@siemens.com> (raw)
In-Reply-To: <CAP9ODKqB8dnsThLVpK=+xC0XPagMGyvT-8Rma3LTP9rds4u7oQ@mail.gmail.com>
Am 16.02.2016 um 12:51 schrieb Otavio Salvador:
> On Tue, Feb 16, 2016 at 9:40 AM, Pascal Bach <pascal.bach@siemens.com> wrote:
>> 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.
> Agreed; I also think 1.9 recipe ought to have default preference as -1
> so users take the stable by default.
>
I agree, but this will change the version for people using nginx not without setting preferred version.
Is this an issue? If not I will update the patchset and set DEFAULT_PREFERENCE for 1.9 to -1
prev parent reply other threads:[~2016-02-17 14:24 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 ` [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 [this message]
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=56C482B0.6020608@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.