<div dir="ltr"><div dir="ltr">On Fri, May 1, 2020 at 10:33 AM Nolan Darilek <<a href="mailto:nolan@thewordnerd.info">nolan@thewordnerd.info</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">
<div>
<p>Also, note that whatever Freedesktop SDK last shipped Python2
will eventually be EOL. I don't know what this means. Not sure if
it eventually gets removed from Flathub along with all its
dependencies. The consequence I encountered was getting spammed on
package upgrades that I had an EOL GNOME platform installed. I
removed the offending package because I didn't use it, so am not
sure how long the dependency would have hung around.</p></div></blockquote><div><br></div><div>I'm not using the freedesktop SDK and am building Python 2.7 from source so that part isn't a problem at least...</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<p>I like Flatpak better, but for the purposes of maintaining
Python2 support for as long as needed, I wonder if AppImages may
be a better bet? You'd have to build your own Python, but you can
then download and freeze all dependencies in a single binary. You
may be able to do something similar with Flatpak, but the major
benefit there is that you can get lots from the SDKs/platforms
without having to vendor your own dependencies. It may also be
possible to grab and freeze dependent SDKs into a CHIRP
repository.<br></p></div></blockquote><div>I barely know how to handle an flatpak, trying to learn Appimage may send me over the edge :) The only reason I'm doing this at all is I don't want people upgrading to Fedora 32 not have access to chirp. We're actually discussing coming out with a ham specific Fedora spin but unfortunately it will not include chirp at this time. <br></div><div><br></div><div>Thanks,</div><div>Richard</div><div>KF5OIM</div></div></div>