[Buildroot] [PATCH v4] package/exiv2: cleanup options and licenses

[Arnout Vandecappelle]

On 06/06/2019 17:15, Yann E. MORIN wrote:
>>  That said, it doesn't really hurt to have a legacy entry, so let's add it after
>> all.
> We did not add such a legacy entry for the Qt5 license drop, there is no
> reason to add one here either.

 For qt5, there was no Config.in option to which we could apply legacy. There
was only the inverse (BR2_PACKAGE_QT5BASE_LICENSE_APPROVED) so we'd have to
trigger legacy in case that option was *not* enabled, which isn't possible.

 I repeat: it doesn't hurt to add a legacy entry, and it may help someone who
thought that they could use the Buildroot exiv2 package for the thing for which
they had a commercial license.

 Regards,
 Arnout