From eebd4241b3636f480d1580e3ed3a391089fb8ecc Mon Sep 17 00:00:00 2001
From: Joe Obo Run <joborun@disroot.org>
Date: Wed, 6 Apr 2022 12:03:15 +0000
Subject: [PATCH] Update 'jobcomm.md'

---
 jobcomm.md | 22 ++++++++++++++++++++--
 1 file changed, 20 insertions(+), 2 deletions(-)

diff --git a/jobcomm.md b/jobcomm.md
index b5993e8..35a681e 100644
--- a/jobcomm.md
+++ b/jobcomm.md
@@ -17,8 +17,8 @@ The pacman.conf entry for this would be:
 <pre>
 
 [jobcomm]
-Server = file:///var/cache/jobcomm/
-#Server = https://osdn.net/projects/joborun/storage/jobextra/
+#Server = file:///var/cache/jobcomm/
+Server = https://osdn.net/projects/joborun/storage/jobextra/
 
 </pre>
 
@@ -38,5 +38,23 @@ I am thinking of jobcomm more like an AUR repository rather than a coordinated j
 
 You can open an issue on this file and discuss this here or in reddit.com/r/joborun  
 
+Alternatively you can fork jobcomm into 2 repositories, your own local repository and the one from osdn indicating of an update.
 
 
+<pre>
+
+[jobcomm]
+Server = https://osdn.net/projects/joborun/storage/jobextra/
+
+[jobcomm0]
+Server = file:///var/cache/jobcomm0/
+
+</pre>
+
+The first notifies you of an upgrade the second is your local fork where you install the one you built.
+
+<pre>
+% sudo pacman -S jobcomm0/palemoon
+</pre>
+
+for example, whose pkgver and pkgrel match the one of jobcomm and only when you see a difference on jobcomm will you know it is time to upgrade, otherwise you are all caught up.