From ea1d86c1bed74a5a104e5bdb98317c7bd8076570 Mon Sep 17 00:00:00 2001
From: KM4ACK <jason.oleham@gmail.com>
Date: Thu, 9 Sep 2021 13:25:09 -0500
Subject: [PATCH] initial

---
 patch/hamlib4.2-20210909 | 35 +++++++++++++++++++++++++++++++++++
 1 file changed, 35 insertions(+)
 create mode 100644 patch/hamlib4.2-20210909

diff --git a/patch/hamlib4.2-20210909 b/patch/hamlib4.2-20210909
new file mode 100644
index 0000000..65365ba
--- /dev/null
+++ b/patch/hamlib4.2-20210909
@@ -0,0 +1,35 @@
+#!/bin/bash
+
+#This patch is for installing hamlib 4.2.
+#20210909 KM4ACK
+
+#Give this patch a unique name. A good idea is
+#to give it the application name that is being 
+#patched followed by the date. ie FLDIDI20210805
+
+PATCHNAME=hamlib4.2-20210909
+
+PATCHFILE=$HOME/.config/patch
+touch $PATCHFILE
+###############################
+#Patch script commands go here#
+###############################
+clear;echo;echo
+echo "applying hamlib 4.2 patch"
+cd $HOME/Downloads
+wget https://github.com/Hamlib/Hamlib/releases/download/4.2/hamlib-4.2.tar.gz
+tar -xzf hamlib-4.2.tar.gz
+rm hamlib-4.2.tar.gz
+cd hamlib-4.2
+./configure
+make
+sudo make install
+sudo ldconfig
+
+#############################################
+#write patch name to a file so we can       #
+#look and see if it has been applied before.#
+#This is checked by the patch-menu script   #
+#before running the patch                   #
+#############################################
+echo "$PATCHNAME" >> $PATCHFILE