From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Adding deprecated packages to legacy [was: cups: deprecate package due to security issues]
Date: Sat, 07 Mar 2015 01:37:32 +0100 [thread overview]
Message-ID: <54FA484C.7000905@mind.be> (raw)
In-Reply-To: <1425649164-31813-1-git-send-email-gustavo@zacarias.com.ar>
On 06/03/15 14:39, Gustavo Zacarias wrote:
> It would probably be better to mark it as a legacy option so users get a
> warning when migrating configuration files, but it would require a
> direct removal for that.
Good point! The legacy handling was added to avoid that selected config options
silently disappear when upgrading, but that's exactly what happens with the
deprecation!
Technically it will be a bit difficult to implement, however. But perhaps
that's just because it's already late and my brain is turned off :-)
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2015-03-07 0:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 13:39 [Buildroot] [PATCH] cups: deprecate package due to security issues Gustavo Zacarias
2015-03-06 14:09 ` Thomas Petazzoni
2015-03-06 14:30 ` Gustavo Zacarias
2015-03-07 0:37 ` Arnout Vandecappelle [this message]
2015-03-16 21:26 ` 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=54FA484C.7000905@mind.be \
--to=arnout@mind.be \
--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