<div dir="ltr"><div dir="ltr">On Wed, May 13, 2020 at 10:11 AM Glenn K0LNY <<a href="mailto:glennervin@cableone.net">glennervin@cableone.net</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div bgcolor="#ffffff">
<div><font size="2" face="Arial">What are the steps now for installing
Chirp?</font></div>
<div><font size="2" face="Arial">I mean, will I have to do a bunch of cryptic Linux
commands to get it installed in the CLI?</font></div></div></blockquote><div><br></div><div>Depends on how your distro manages flatpaks. The command line "flatpak install ..." method is certainly available but at least on Fedora it also integrates with the Software app IF the flatpak is in a repo.</div><div><br></div><div>Currently I'm only providing a standalone file. Additionally I have the chirp version in the filename which is both a good and bad thing.</div><div><br></div><div>I'ts good because you know what version you're installed, it's bad because you could potentially install multiple versions since they have different names. I haven't tested this yet.</div><div><br></div><div>Short term you can remove the old version before installing the new version. Medium term I can look at getting it into a public Flatpak repo.</div><div><br></div><div>Long term the solution HAS to be to get chirp running on Python 3 / Gtk 3.</div><div><br></div><div>Thanks,</div><div>Richard</div></div></div>