Merge remote-tracking branch

'origin/GP-6228_d-millar_protobuf_docs--SQUASHED' (Closes #8774)

Ghidra/Debug/Debugger-agent-dbgeng/src/main/help/help/topics/dbgeng/dbgeng.html

@@ -48,7 +48,7 @@
     <UL style="list-style-type: none">
       <LI>
 <PRE>
-python3 -m pip install pybag protobuf==3.20.3
+python3 -m pip install pybag protobuf>=3.20.3
 </PRE>
       </LI>
     </UL>

Ghidra/Debug/Debugger-agent-gdb/src/main/help/help/topics/gdb/gdb.html

@@ -38,7 +38,7 @@
     <UL style="list-style-type: none">
       <LI>
 <PRE>
-python3 -m pip install psutil protobuf==3.20.3
+python3 -m pip install psutil protobuf>=3.20.3
 </PRE>
       </LI>
     </UL>

Ghidra/Debug/Debugger-agent-lldb/src/main/help/help/topics/lldb/lldb.html

@@ -38,7 +38,7 @@
     <UL style="list-style-type: none">
       <LI>
 <PRE>
-python3 -m pip install psutil protobuf==3.20.3
+python3 -m pip install psutil protobuf>=3.20.3
 </PRE>
       </LI>
     </UL>

Ghidra/Debug/Debugger-rmi-trace/DEVNOTES.txt

@@ -117,8 +117,6 @@ That said, for unit testing, I've had to incorporate package installation as a @
 There's probably a better way, and that way may also help with out-of-the-box support.
 Something like setting PYTHON_PATH before invoking the debugger?
 There's still the issue of installing protobuf, though.
-And the version we use is not the latest, which may put users who already have protobuf in dependency hell.
-We use version 3.20, while the latest is 4.something.
 According to protobuf docs, major versions are not guaranteed backward compatible.
 To upgrade, we'd also have to upgrade the Java side.
 

Ghidra/Debug/Debugger-rmi-trace/src/main/help/help/topics/TraceRmiLauncherServicePlugin/TraceRmiLauncherServicePlugin.html

@@ -134,7 +134,7 @@
     <UL style="list-style-type: none">
       <LI>
 <PRE>
-python3 -m pip install protobuf==3.20.3
+python3 -m pip install protobuf>=3.20.3
 </PRE>
       </LI>
     </UL>

GhidraDocs/GettingStarted.md

@@ -165,7 +165,7 @@ The Debugger now uses Python to connect to the host platform's native debuggers.
 a [supported](#minimum-requirements) version of Python and some additional packages. These packages
 are included in the distribution, but you may still install them from PyPI if you prefer:
 * psutil
-* protobuf==3.20.3
+* protobuf>=3.20.3
 * Pybag>=2.2.12 (for WinDbg support)
 
 Different native debuggers have varying requirements, so you do not necessarily have to install all

GhidraDocs/GhidraClass/Debugger/B1-RemoteTargets.html

@@ -287,7 +287,7 @@ the Python source over and add it to your <code>PYTHONPATH</code>.</p>
 <p>Double-check that you have installed all the required packages and
 their dependencies. A common forgotten or incorrectly-versioned
 dependency is <code>protobuf</code>. We developed using
-<code>protobuf==3.20.3</code>. Its “sdist” package is distributed with
+<code>protobuf==3.20.3</code>, newer versions generally work fine. Its “sdist” package is distributed with
 Ghidra under <code>Debugger-rmi-trace/pypkg/dist</code> for your
 convenience.</p>
 <p>It is also possible that <code>gdb</code> has embedded a different

GhidraDocs/GhidraClass/Debugger/B1-RemoteTargets.md

@@ -126,7 +126,7 @@ If that doesn't work, then in the worst case, copy the Python source over and ad
 
 Double-check that you have installed all the required packages and their dependencies.
 A common forgotten or incorrectly-versioned dependency is `protobuf`.
-We developed using `protobuf==3.20.3`.
+We developed using `protobuf==3.20.3`, newer versions generally work fine.
 Its "sdist" package is distributed with Ghidra under `Debugger-rmi-trace/pypkg/dist` for your convenience.
 
 It is also possible that `gdb` has embedded a different version of the interpreter than the one that `python3` provides.