From 0fc5105da1293b25225d4e5a912a7fcf2d2522ee Mon Sep 17 00:00:00 2001
From: KM4ACK <jason.oleham@gmail.com>
Date: Wed, 1 Sep 2021 17:23:56 -0500
Subject: [PATCH] initial commit

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

diff --git a/patch/hamlib4.2 b/patch/hamlib4.2
new file mode 100644
index 0000000..e5a9839
--- /dev/null
+++ b/patch/hamlib4.2
@@ -0,0 +1,39 @@
+#!/bin/bash
+
+#This script will install hamlib 4.2 until
+#hamlib 4.3 can be fixed. See this issue
+#https://github.com/km4ack/pi-build/issues/296
+#20210901 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-20210901
+
+PATCHFILE=$HOME/.config/patch
+touch $PATCHFILE
+###############################
+#Patch script commands go here#
+###############################
+clear;echo;echo
+echo "This is a test 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