basslik
macrumors 6502a
I'll wait for the beta testers😁iMac 2011 with Nvidia K2100m. I read in the changelog there are improvements for older CPUs, so I did it...
I'll wait for the beta testers😁iMac 2011 with Nvidia K2100m. I read in the changelog there are improvements for older CPUs, so I did it...
I did that the first time, rebooted twice after that. Still getting the dirty volume message with a few patches teasing me.In fact, I did not state the order of operations completely right. What I did was:
Open OCLP app --> confirm update message and update --> Install OC to disk --> get error message "dirty volume" --> Click Post-Install Patch and Revert patches --> reboot --> Confirm OCLP message and apply new root patches --> reboot.
Understandable, but as I see it, 2.5.0n has been tested for around a year now, so I just did it. No problems so far.I'll wait for the beta testers😁
Third times a charm!I did that the first time, rebooted twice after that. Still getting the dirty volume message with a few patches teasing me.
sameYes, after updating the root patches it should say something like all avaible patches are already installed, but instead seems to be offering them again, even if they have been correctly updated
I would create a new container, and try it that way.same
Right now it says 15.7.9 is the latest, and what I'm downloading to refresh the installer. Is this the way to go for now, for Sequoia? I thought about going with Sonoma, since it can be better for certain things when it comes to stability.
I upgraded my late 2015 27-inch 5K iMac again to sequoia today from Monterey using 15.7.9 and the official release of 2.5.0. It's not bad, and everything seems to work including my custom compiled stuff. I still think Monterey is the best version of macOS when it comes to a balance between a modern OS and performance. Apple is increasingly making it hard though to keep an older version unless I switch to open source, which I did for many things.It's hard to give blanket advice. The "best practice" depends on your specific hardware and the software you want to run.
Personally, I don't bother with the beta versions of macOS on my OCLP machine, nor do I use beta/nightly builds of OCLP.
My blanket recommendation is to read the OCLP FAQ thoroughly, and then to read the specific notes for Sequoia and Sonoma, paying particular attention to the "Issues" sections. Choose the OS that is most likely to do what you want on the machine you want to use. That said, keep in mind that if Apple continues past practices, August 2026's Sonoma 14.8.9 probably is Sonoma's final scheduled security update.
FWIW, I've been using Sequoia 15.7.9 and OCLP 2.4.x on my mid-2012 13" MBP, though I updated OCLP to 2.5.0 official release today.
It seems like Apple has gotten rid of Xcode and replaced it with Apple Developer. I know this because Xcode doesn't show up in searches anymore; just in my purchase history.
Do a search for Xcode in the Mac App store, when I did, it returned Apple Developer, without any Xcode results. I had to update Xcode to the latest for Sequoia through my purchase history. Also, I had to drag my existing binary from binary to the trash first, and then I was able to install 26.6.3. Anything beyond that is Tahoe, and newer. Here is a screenshot to back up my claim, and experience.I'm not sure what you mean by that. Xcode remains a central component of the macOS development. It's not installed by default, but it's easy enough to get.
Do a search for Xcode in the Mac App store, when I did, it returned Apple Developer, without any Xcode results. I had to update Xcode to the latest for Sequoia through my purchase history. Also, I had to drag my existing binary from binary to the trash first, and then I was able to install 26.6.3. Anything beyond that is Tahoe, and newer. Here is a screenshot to back up my claim, and experience.
Thanks for the heads up. I didn't realize the visibility had changed based on version. When I saw that, I got the impression Apple changed Xcode into Apple Developer and that was the new name for it going forward. Also keep in mind that I haven't been following Xcode either, as I had built llvm from source, as well as several versions of GCC so I could keep current independent of Apple since I usually don't build native apple tools, but cross platform open source tools. In fact in terms of security updates and patching my own system, I was doing well with that on Monterey, it's more the pre-compiled native macOS binaries that were falling behind in support, and I haven't found open source alternatives for everything yet.Current Xcode require Tahoe 25.2+ and won't show for earlier macOS - for past macOS releases always use www.xcodereleases.com
Thanks for the heads up. I didn't realize the visibility had changed based on version. When I saw that, I got the impression Apple changed Xcode into Apple Developer and that was the new name for it going forward. Also keep in mind that I haven't been following Xcode either, as I had built llvm from source, as well as several versions of GCC so I could keep current independent of Apple since I usually don't build native apple tools, but cross platform open source tools. In fact in terms of security updates and patching my own system, I was doing well with that on Monterey, it's more the pre-compiled native macOS binaries that were falling behind in support, and I haven't found open source alternatives for everything yet.
Thanks for the heads up. I didn't realize the visibility had changed based on version. When I saw that, I got the impression Apple changed Xcode into Apple Developer and that was the new name for it going forward.
It was always searchable until Tahoe came out. And yes it shows up in my purchase history as well.The only time you'd see Xcode in the App Store on an older version of macOS is if it is already installed, when it would say that you need to upgrade macOS to use the latest Xcode, or in your list of "Purchased" apps.
Am I mistaken in thinking the 26.x versions require Apple Silicon? For Intel I believe you'd need Xcode 16.x, though Homebrew complains about it.Direct link for Xcode 26.3 for Sequoia https://developer.apple.com/service...per_Tools/Xcode_26.3/Xcode_26.3_Universal.xip
We are using 26.5 on Intel FWIW so I would think this is not quite correct. But on Tahoe and supported MacAm I mistaken in thinking the 26.x versions require Apple Silicon? For Intel I believe you'd need Xcode 16.x, though Homebrew complains about it.
Am I mistaken in thinking the 26.x versions require Apple Silicon? For Intel I believe you'd need Xcode 16.x, though Homebrew complains about it.
Interesting. I've previously downloaded Xcode command line tools for 26.3 for that very reason. When i ran the installer I got a message that it wouldn't install on my OCLP iMac with 15.7.8. Perhaps I'll try the full Xcode installer and see how it goes.If you take a look on xcodereleases.com you’d see that Xcode 26.x are also for Intel Macs, for 26.3 the requirement is just Sequoia 15.6+, see below.