From: Arne Fitzenreiter <arne_f@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] intel-microcode: add new package
Date: Sat, 22 Jun 2019 11:16:52 +0100 [thread overview]
Message-ID: <1561198612-5058-1-git-send-email-arne_f@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1699 bytes --]
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
---
intel-microcode/intel-microcode.nm | 40 ++++++++++++++++++++++++++++++++++++++
1 file changed, 40 insertions(+)
create mode 100644 intel-microcode/intel-microcode.nm
diff --git a/intel-microcode/intel-microcode.nm b/intel-microcode/intel-microcode.nm
new file mode 100644
index 0000000..1232a93
--- /dev/null
+++ b/intel-microcode/intel-microcode.nm
@@ -0,0 +1,40 @@
+###############################################################################
+# IPFire.org - An Open Source Firewall Solution #
+# Copyright (C) - IPFire Development Team <info(a)ipfire.org> #
+###############################################################################
+
+name = intel-microcode
+version = 20190618
+release = 1
+arch = noarch
+thisapp = microcode-%{version}
+
+maintainer = Arne Fitzenreiter <arne.fitzenreiter(a)ipfire.org>
+groups = System/Libraries
+url = https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases
+license = Non-GPL
+summary = Microcode update for Intel CPU's.
+
+description
+ intel-microcode provides some binaries that
+ are loaded into the Intel CPU at startup.
+end
+
+source_dl = https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/archive/
+
+build
+ build
+ : # Nothing to do.
+ end
+
+ DIR_APP = %{DIR_SRC}/Intel-Linux-Processor-Microcode-Data-Files-%{thisapp}
+
+ install
+ mkdir -pv %{BUILDROOT}%{prefix}/lib/firmware
+ cp -prv intel-ucode %{BUILDROOT}%{prefix}/lib/firmware
+ end
+end
+
+packages
+ package %{name}
+end
--
2.6.3
reply other threads:[~2019-06-22 10:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1561198612-5058-1-git-send-email-arne_f@ipfire.org \
--to=arne_f@ipfire.org \
--cc=development@lists.ipfire.org \
/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