<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><blockquote type="cite" class=""><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class="">Can you explain any practical justification for supporting Leopard on
Intel?
I'm not suggesting that it's in any way "wrong" but I just can't see
where the utility for such machines is. I'm still making use of a 2006
Core Duo iMac which is 10.6/i386, so I'm familiar with the fact that the
very first Intel Mac can run 10.6 and that for a variety of reasons it
is a generally good idea to do that update. I'm curious about what your
thinking is.
</pre></blockquote><div class=""><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class=""><br class=""></pre><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class="">No doubt, it is the lowest on my list, and I fix the other compilers, linkers, and cctools first. But it has some uses. </pre><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class=""><br class=""></pre><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class="">I have a MacMini 1,1 with 1GB of Ram that runs either MacOS X 10.4 or 10.5. It doesn’t have enough ram to run 10.6. Perhaps I can upgrade it, but that would be a soldering project. I use it to build TenFourFox for Intel which I upload to the TenFourFox SourceForge site, amongst other things.</pre><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class=""><br class=""></pre><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class="">For building things for 10.4 and 10.5 PPC (of which I currently have 8 running machines) it’s sometimes handy to buzz something up on 10.4 or 10.5 Intel. For example my 10.5 VM runs with 8 processors and 16 GB of RAM on a dual Quad-Core Intel Xeon, so I can build things very quickly there to test out build issues.</pre><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class=""><br class=""></pre><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class="">And there are people (like Riccardo, and many others) who are just stuck on the nostalgia or the system or the software they have or … who knows why? If MacPorts _can_ support them without too much trouble, and if there are interested people around like me and others who don’t mind doing it from time to time — why not? It’s all one big family, and keeps people in MacPorts rather than floating off to the other options.</pre><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class=""><br class=""></pre><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class="">You’ll be really happy with the 68030 SE/30 that is currently running on my desk, and the 30 other Mac systems I keep running here in the Mac Museum :></pre><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class=""><br class=""></pre><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class="">I would not dare to interfere with progress — if there is a decision that involves moving MacPorts forward to arm64 vs maintaining support for 10.4 Intel, well that is not even a question to ask.</pre><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class=""><br class=""></pre><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class="">I have ways for that. libSDL2 runs fairly well on 10.4 and 10.4 PPC and Intel, but I keep that in my custom overlays for people to find. So hopefully no sweat off anyone’s brow about this.</pre><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class=""><br class=""></pre><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class="">Ken</pre><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class=""><br class=""></pre></div></body></html>