From: Khem Raj <raj.khem@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
akuster808 <akuster808@gmail.com>
Cc: Adrian Bunk <bunk@stusta.de>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bind: Remove RECIPE_NO_UPDATE_REASON and follow the ESV releases
Date: Tue, 30 Jul 2019 11:02:40 -0700 [thread overview]
Message-ID: <5f784845-62c8-8a50-a05a-4a7eba319199@gmail.com> (raw)
In-Reply-To: <CANNYZj8XyDdF_VNHL_YiDcFXeXf4Pk=o-pqg2SD3TO32ozqbyw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
On 7/30/19 6:01 AM, Alexander Kanavin wrote:
> On Tue, 30 Jul 2019 at 11:21, akuster808 <akuster808@gmail.com
> <mailto:akuster808@gmail.com>> wrote:
>
> So are you setting the package update policy to LTS only ? Its a
> function over maintenance question.
>
> I don't understand why this package is being singled out. I think it
> should be an OE architecture discussion
>
>
> I am not sure why are you objecting to this. This line:
> RECIPE_NO_UPDATE_REASON = "9.11 is LTS 2021"
> was added by you, and more or less states that update policy for bind
> is LTS-only.
I see a technical reason where dependent packages like dhcp expects 9.11
if used from system, there is an option to built the bundled version of
bind9 but that results in duplication. Unless there are other compelling
reason for upgrading, I would like us to stick with 9.11
>
> Alex
>
[-- Attachment #2: Type: text/html, Size: 2441 bytes --]
prev parent reply other threads:[~2019-07-30 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 10:00 [PATCH] bind: Remove RECIPE_NO_UPDATE_REASON and follow the ESV releases Adrian Bunk
2019-07-30 9:20 ` akuster808
2019-07-30 9:47 ` Adrian Bunk
2019-07-30 13:01 ` Alexander Kanavin
2019-07-30 18:02 ` Khem Raj [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=5f784845-62c8-8a50-a05a-4a7eba319199@gmail.com \
--to=raj.khem@gmail.com \
--cc=akuster808@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=bunk@stusta.de \
--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