Why is an update that ostensibly fixes one little issue 1.56 GB in size ¯\_(ツ)_/¯
Conversation
Notices
-
Embed this notice
Thomas 🔭🕹️ (thomasfuchs@hachyderm.io)'s status on Saturday, 02-Sep-2023 04:20:11 JST Thomas 🔭🕹️ -
Embed this notice
Thomas 🔭🕹️ (thomasfuchs@hachyderm.io)'s status on Saturday, 02-Sep-2023 04:28:33 JST Thomas 🔭🕹️ @froztbyte M1 Max here fwiw
-
Embed this notice
JP (froztbyte@mastodon.social)'s status on Saturday, 02-Sep-2023 04:28:34 JST JP @thomasfuchs haha it said 751MB for my M1 (but I guess it’s a two-stager as was mentioned in that post that was recently kicking around), but I had the same reaction
Even checked the security announces, nothing there. Keen to see a patch diff
-
Embed this notice
Thomas 🔭🕹️ (thomasfuchs@hachyderm.io)'s status on Saturday, 02-Sep-2023 05:12:06 JST Thomas 🔭🕹️ @danherbert This seems... suboptimal.
-
Embed this notice
Dan Herbert (danherbert@mastodon.social)'s status on Saturday, 02-Sep-2023 05:12:08 JST Dan Herbert @thomasfuchs That's thanks to a MacOS security feature introduced in Sierra 10.12 called "Gatekeeper*" that requires whole disk images to be signed to protect from being modified. It means even small patches have to completely replace large chunks of the system to update.
*Gatekeeper has technically been around for a while, but only added that extra feature starting in Sierra.
-
Embed this notice
Thomas 🔭🕹️ (thomasfuchs@hachyderm.io)'s status on Saturday, 02-Sep-2023 06:23:33 JST Thomas 🔭🕹️ @danherbert :blobfoxgoogly:
-
Embed this notice
Dan Herbert (danherbert@mastodon.social)'s status on Saturday, 02-Sep-2023 06:23:34 JST Dan Herbert @thomasfuchs It's more suboptimal than you'd think. Part of the update size is because Apple chooses to have a single disk image for all supported architectures, so ARM & Intel updates are included for everyone regardless of your system type, which makes updates even bigger.
-
Embed this notice