[FEATURE REQUEST] Please create a universal binary for the MacOS installer instead of separate arm64 and x86_64 versions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Is your feature request related to a problem? Please describe.
As a user and salt administrator, my life would be much simpler and my fleet of managed hosts much better managed if I could deploy one salt installer irrespective of whether the target computer was intel or ARM-based. It would remove some client-side logic and condition checking during installations and upgrades.
Describe the solution you'd like
I would like there to be a salt-300X.Y-onedir-macos-universal.tar.xz and salt-300X.Y-py3-universal.pkg installation package that contains a single set of universal binaries.
Describe alternatives you've considered
Currently all salt installations have to do an evaluation of the target architecture before launching the appropriate installer package. It works but this would be much more elegant and is the best-practice method now.
Additional context
CMake and other OSS build tools have supported macOS universal binaries for a while now, the build targets just need to specify both archs in the DCMAKE argument, e.g. -DCMAKE_OSX_ARCHITECTURES="arm64;x86_64"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating Salt's macOS installer build configuration and packaging entry points; the issue does not name specific files or tests. Check how the arm64 and x86_64 onedir tarball and py3 package are produced, then verify that the requested universal artifacts install and run on both architectures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, macos, python
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100