<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Cameron -</p>
<p> thank you for bringing this up -- I have written extensively in
IRC chat on this topic at least twice since 2009. The technical
details are not that difficult, but not easy to list exhaustively
without some effort. More from a marketing and user-advocate point
of view, I think that it can be summed up very well, as follows:</p>
<p> the osgeolive QGis stack, all the plugins and associated
services, connected in a functional way, can be thought of as a
graph.</p>
<p> similarly, all the web-facing services, all the plugins and
associated services, connected with their dependancies in terms of
the dot-deb or installer script that installs them, can also be
thought of as a graph</p>
<p> the difference between those two graphs.. what is ONLY in one
graph versus what is ONLY in the other graph, are in fact, a very
decent first aproximation of the difference between the osgeolive
that we ship now, versus what a "cloud" osgeolive would be</p>
<p> I believe Angelos knows this very well, and I welcome input or
repudiation, from any community member</p>
<p> thank you and best regards from Berkeley, Calif --Brian M
Hamlin / MAPLABS /</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 2/7/22 10:43 AM, Cameron Shorter
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CABqeU+iHxxRSRUBVGXZ5UGcJBHgZXoaALk3C1unqEq5o-Gq-tw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Something which is getting more-and-more feasible
every year is to run OSGeo-Live as a virtual machine in the
cloud.
<div><a
href="http://cameronshorter.blogspot.com/2009/10/try-open-source-geospatial-desktop.html"
moz-do-not-send="true">We actually managed to do this back
in 2009</a>, but the partners working on it got stuck in the
following release.</div>
<div>Someone might want to take another look at this approach? </div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, 8 Feb 2022 at 01:47,
James Klassen <<a href="mailto:jklassen@sharedgeo.org"
moz-do-not-send="true">jklassen@sharedgeo.org</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>
<div dir="auto">There was discussion awhile back about
supporting ARM for Raspberry Pi and similar SBCs that
came to the same conclusion that it would take more
developer resources that were available. </div>
<div dir="auto"><br>
</div>
<div dir="auto"><span
style="border-color:rgb(0,0,0);color:rgb(0,0,0)">OSGeo
Live is meant to “just work” </span><span
style="border-color:rgb(0,0,0);color:rgb(0,0,0)">to
encourage new users explore the software without
having to first face the learning curve of getting it
installed and configured correctly. That is a lot
more difficult to accomplish when users face to face
the variations inherent in running different
architectures. </span><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Most, but not all of the packages that go
into OSGeo Live are available on ARM (are in Ubuntu-GIS
and Debian-GIS or are platform agnostic and install the
same files as on x86). So, technically it isn’t too far
fetched. But, if I remember correctly, pain points are
testing and documentation. I’d venture a guess that, by
far, nearly all of the developer time on OSGeo Live is
spent on testing and documentation.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Another issue with ARM is that while the
user space is the same/similar across ARM devices, a
bootable image (like we do with x86) would have to be
tailored to each device. Maybe there would be a way to
just provide a user space and have the user provide the
matching version of Ubuntu for their machine. Maybe the
whole thing could be built into a snap or flatpak or
appimage. It would still be a different experience than
we’ve traditionally had for x86 which raises
documentation and ease of use concerns. </div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">I’m also a bit surprised the M1 Macs can’t
run x86 OSes in emulation. There were programs that
emulated a PC to allow 68k and PowerPC era Macs to run
DOS/Windows.</div>
</div>
</div>
<div>
<div>
<div dir="auto"><br>
</div>
<div dir="auto">On Sat, Feb 5, 2022 at 04:06 Angelos
Tzotsos <<a href="mailto:gcpp.kalxas@gmail.com"
target="_blank" moz-do-not-send="true">gcpp.kalxas@gmail.com</a>>
wrote:<br>
</div>
</div>
<div>
<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">Dear Barend,<br>
<br>
We do not have an ARM version. This would require
more developer <br>
resources than we currently have, so there is
currently no plan to <br>
support this architecture.<br>
<br>
Best,<br>
Angelos<br>
<br>
On 2/2/22 01:24, Kobben, Barend (UT-ITC) wrote:<br>
> For installation in the Parallels virtual
machine on a new MacPro (running on the Apple
silicon architecture), an ARM version instead of an
Intel version is needed. Is that available, or will
in be...? Or are there alternative ways to get it
running on a Mac M1...?<br>
><br>
> --<br>
> Barend Köbben<br>
> Senior Lecturer – ITC-GIP & ATLAS,
University Twente<br>
> PO Box 217, 7500 AE Enschede (The Netherlands)<br>
> +31-(0)53 4874 253 / room 1-065 ITC<br>
><br>
> _______________________________________________<br>
> osgeolive mailing list<br>
> <a href="mailto:osgeolive@lists.osgeo.org"
target="_blank" moz-do-not-send="true">osgeolive@lists.osgeo.org</a><br>
> <a
href="https://lists.osgeo.org/mailman/listinfo/osgeolive"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/osgeolive</a><br>
<br>
<br>
-- <br>
Angelos Tzotsos, PhD<br>
President<br>
Open Source Geospatial Foundation<br>
<a href="http://users.ntua.gr/tzotsos"
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://users.ntua.gr/tzotsos</a><br>
<br>
_______________________________________________<br>
osgeolive mailing list<br>
<a href="mailto:osgeolive@lists.osgeo.org"
target="_blank" moz-do-not-send="true">osgeolive@lists.osgeo.org</a><br>
<a
href="https://lists.osgeo.org/mailman/listinfo/osgeolive"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/osgeolive</a><br>
</blockquote>
</div>
</div>
</div>
</div>
_______________________________________________<br>
osgeolive mailing list<br>
<a href="mailto:osgeolive@lists.osgeo.org" target="_blank"
moz-do-not-send="true">osgeolive@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/osgeolive"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/osgeolive</a><br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div>
<div><span style="font-size:12.8px">Cameron
Shorter</span><br>
</div>
<div>Technical Writer, Google</div>
</div>
<div><br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
osgeolive mailing list
<a class="moz-txt-link-abbreviated" href="mailto:osgeolive@lists.osgeo.org">osgeolive@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/osgeolive">https://lists.osgeo.org/mailman/listinfo/osgeolive</a>
</pre>
</blockquote>
</body>
</html>