On Di, 2016-10-04 at 16:19 +0200, Michael Olbrich wrote:
> In this case, I'd say, let's just move the package to staging and not use
> it at all. As I noted in my other mail, even ntp is not using it any more,
> so it is no longer needed.
ACK. Just sent a patch, with some information why:
"libmd:
On Mon, Oct 03, 2016 at 10:18:56PM +0200, Andreas Pretzsch wrote:
> While updating the license stuff in a customer BSP, libmd hit me.
>
> libmd provides MD2, MD4, MD5, SHA-1 and RIPEMD-160 message digest
> algorithms.
> Each of the respective implementations includes different license
>
Hi,
> One option is of course to simply ignore it, i.e. not use it ;-)
I don't think this is a good option ;-)
> […]
> Now, as I have this can of worms open anyway, what would be the best way
> to specify a license tag ?
Apparently util-linux is similar to that, its README.licenses says:
>
While updating the license stuff in a customer BSP, libmd hit me.
libmd provides MD2, MD4, MD5, SHA-1 and RIPEMD-160 message digest
algorithms.
Each of the respective implementations includes different license
statements, with wrappers under beer-ware license.
Copied them in below, for reference.
