From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2018-02-25
Date: Thu, 01 Mar 2018 22:17:32 +0100 [thread overview]
Message-ID: <87inafh4wj.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <096b2356-52d1-ee4d-0dc4-504d4a0dfee7@mind.be> (Arnout Vandecappelle's message of "Thu, 1 Mar 2018 20:41:13 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> Makes me think that we won't be able to do a good job supporting it
>> throughout the 2018.02 support cycle.
> Well, for most packages, the "support" is limited to "it's still there and it
> still doesn't fail in autobuilders".
I was hoping for a bit more than that, E.G. has no known security
issues.
> Which will not happen because we don't use any new toolchains or
> anything during the LTS support cycle.
Unless there is a security issue in one of the libraries it uses (like
openssl) and we need to bump the version to fix that issue.
>> We don't have a good way of handling deprecations, so I'm not sure what
>> the best option is:
>>
>> - Do nothing
>> - Change prompt to "Qt (obsolete)"
> I like this one. It costs us nothing, it makes it clear that you can't expect
> support updates on this package, and it's an advance warning that it may be removed.
Ok, I'll send a patch.
>> - Remove package
> Eventually, yes, with legacy handling. I would remove it only when it breaks.
Ok.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-03-01 21:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-02-25 Thomas Petazzoni
2018-02-26 10:33 ` [Buildroot] Analysis of build " Thomas Petazzoni
2018-02-26 10:51 ` Johan Oudinet
2018-02-26 10:58 ` Thomas Petazzoni
2018-02-26 13:44 ` Frank Hunleth
2018-02-26 12:48 ` Peter Korsgaard
2018-02-26 13:00 ` Thomas Petazzoni
2018-02-26 14:06 ` Peter Korsgaard
2018-02-26 14:47 ` Thomas Petazzoni
2018-02-26 19:01 ` Peter Korsgaard
2018-03-01 19:41 ` Arnout Vandecappelle
2018-03-01 21:17 ` Peter Korsgaard [this message]
2018-02-27 12:08 ` Peter Seiderer
2018-02-27 13:12 ` Peter Korsgaard
2018-02-26 15:30 ` Mahyar Koshkouei
2018-02-26 15:40 ` Thomas Petazzoni
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=87inafh4wj.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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