mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Andreas Pretzsch <apr@cn-eng.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] libmd: move to staging (license issues and no more users inside ptxdist)
Date: Tue,  4 Oct 2016 18:09:04 +0200	[thread overview]
Message-ID: <1475597344-3280-1-git-send-email-apr@cn-eng.de> (raw)

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.
None of them is specified or extracted in the ptxdist rule.
In addition, to handle esp. the RSA license on MD2 and MD4, some build config
parameters should be introduced to be able to remove them.

In ptxdist, ntp was the only direct user of libmd, but provides its internal
MD5 implementation by now. This one is used if no libmd or similar is found.
From an incomplete check, libarchive can also make use of libmd, but prefers
OpenSSL/libcrypto, as being more complete.

Last, package seems to be not updated since 2009.

So instead of fixing all of the above, move to staging, so it can be removed
some day, unless somebody needs it and picks up above tasks.

Signed-off-by: Andreas Pretzsch <apr@cn-eng.de>
---
 rules/libmd.in | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/rules/libmd.in b/rules/libmd.in
index 7e8e0e1..6b19ad8 100644
--- a/rules/libmd.in
+++ b/rules/libmd.in
@@ -1,4 +1,6 @@
-## SECTION=system_libraries
+## SECTION=staging
+## old section:
+### SECTION=system_libraries
 menuconfig LIBMD
 	tristate
 	prompt "libmd                         "
-- 
2.9.3


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2016-10-04 16:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-04 16:09 Andreas Pretzsch [this message]
2016-10-05 13:01 ` Michael Olbrich

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=1475597344-3280-1-git-send-email-apr@cn-eng.de \
    --to=apr@cn-eng.de \
    --cc=ptxdist@pengutronix.de \
    /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