[Buildroot] Adding deprecated packages to legacy [was: cups: deprecate package due to security issues]

Arnout Vandecappelle arnout at mind.be
Sat Mar 7 00:37:32 UTC 2015


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


More information about the buildroot mailing list