mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Cc: Clemens Gruber <clemens.gruber@pqgruber.com>
Subject: [ptxdist] [PATCH] minisign: new package
Date: Tue, 24 Oct 2023 15:42:35 +0200	[thread overview]
Message-ID: <20231024134235.17953-1-clemens.gruber@pqgruber.com> (raw)

---
 rules/minisign.in   | 13 +++++++++++
 rules/minisign.make | 57 +++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 70 insertions(+)
 create mode 100644 rules/minisign.in
 create mode 100644 rules/minisign.make

diff --git a/rules/minisign.in b/rules/minisign.in
new file mode 100644
index 000000000..d1efe3b45
--- /dev/null
+++ b/rules/minisign.in
@@ -0,0 +1,13 @@
+## SECTION=applications
+
+config MINISIGN
+	tristate
+	prompt "minisign"
+	select HOST_CMAKE
+	select GCCLIBS_GCC_S
+	select LIBC_M
+	select LIBSODIUM
+	help
+	  Minisign is a dead simple tool to sign files and verify signatures.
+	  It is portable, lightweight, and uses the highly secure Ed25519
+	  public-key signature system.
diff --git a/rules/minisign.make b/rules/minisign.make
new file mode 100644
index 000000000..a90cad200
--- /dev/null
+++ b/rules/minisign.make
@@ -0,0 +1,57 @@
+# -*-makefile-*-
+#
+# Copyright (C) 2023 by Clemens Gruber <clemens.gruber@pqgruber.com>
+#
+# For further information about the PTXdist project and license conditions
+# see the README file.
+#
+
+#
+# We provide this package
+#
+PACKAGES-$(PTXCONF_MINISIGN) += minisign
+
+#
+# Paths and names
+#
+MINISIGN_VERSION	:= 0.11
+MINISIGN_MD5		:= 1565d40ec75b9602e84379c9f1e96371
+MINISIGN		:= minisign-$(MINISIGN_VERSION)
+MINISIGN_SUFFIX		:= tar.gz
+MINISIGN_URL		:= https://github.com/jedisct1/minisign/archive/refs/tags/$(MINISIGN_VERSION).$(MINISIGN_SUFFIX)
+MINISIGN_SOURCE		:= $(SRCDIR)/$(MINISIGN).$(MINISIGN_SUFFIX)
+MINISIGN_DIR		:= $(BUILDDIR)/$(MINISIGN)
+MINISIGN_LICENSE	:= ISC
+MINISIGN_LICENSE_FILES	:= file://LICENSE;md5=ae8e10a2c8237f13943f14fa3ffe437a
+
+# ----------------------------------------------------------------------------
+# Prepare
+# ----------------------------------------------------------------------------
+
+#
+# cmake
+#
+MINISIGN_CONF_TOOL	:= cmake
+MINISIGN_CONF_OPT	:= \
+	$(CROSS_CMAKE_USR)
+
+# ----------------------------------------------------------------------------
+# Target-Install
+# ----------------------------------------------------------------------------
+
+$(STATEDIR)/minisign.targetinstall:
+	@$(call targetinfo)
+
+	@$(call install_init,  minisign)
+	@$(call install_fixup, minisign,PRIORITY,optional)
+	@$(call install_fixup, minisign,SECTION,base)
+	@$(call install_fixup, minisign,AUTHOR,"Clemens Gruber <clemens.gruber@pqgruber.com>")
+	@$(call install_fixup, minisign,DESCRIPTION,missing)
+
+	@$(call install_copy, minisign, 0, 0, 0755, -, /usr/bin/minisign)
+
+	@$(call install_finish, minisign)
+
+	@$(call touch)
+
+# vim: syntax=make
-- 
2.42.0




             reply	other threads:[~2023-10-26  6:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 13:42 Clemens Gruber [this message]
2023-11-10  7:51 ` 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=20231024134235.17953-1-clemens.gruber@pqgruber.com \
    --to=clemens.gruber@pqgruber.com \
    --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