How many externals are there, really? For those that use pd-lib-builder, it's a simple recompile.
I'd argue that more time has been spent writing emails on this issue than it would take for each person to take one external, make a fat build, and upload to deken.
We went through this already with the transition from Pd-extended end-of-life to Pd vanilla + deken: there was much handwrining about the extended externals not being easy to install until someone (IOhannes) simply put the existing compiled externals on deken.
We know what needs to be done, so let's do it.
Message: 1Date: Wed, 30 Mar 2022 12:24:02 +0200From: Christof Ressi <info@christofressi.com>To: Pd-List <pd-list@lists.iem.at>Subject: Re: [PD] [PD-announce] Pd 0.52-2 releasedMessage-ID: <482236c3-8edb-7f21-6156-e18cc9035fd6@christofressi.com>Content-Type: text/plain; charset=UTF-8; format=flowedNow *I* am utterly confused.now people seem to all agree that it was much better way back then.
I think everybody agrees that there should be an ARM64 binary for macOS. The question is just whether it should be the default on M1 machines when there are so few ARM64 externals for macOS available on Deken. (I count 9: zexy, comport, xsample, pool, clk, absattr, vasp, zconf, constantq~)Actually, this issue already came up two months ago and someone called it a "lousy UX":https://lists.puredata.info/pipermail/pd-list/2022-01/130772.htmlSo what has changed?---As I said before, we might alternatively add a disclaimer to the download page that people might want to force-run Pd under Rosetta if they don't find all the externals they need.However, I'm not a Mac user and I don't have a ball in this game. I was just parotting what I thought the consensus was back then...Christof