T27-42 — Audit the DMG script and verify both macOS architectures build

Abierto
#62 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
macos, rust, shell
Área
build-system

Línea de trabajo

Read packaging/build-macos-dmg.sh, docs/TOOLCHAINS.md, and section 3.3 of docs/RELEASE-ENGINEERING-PLAN.md to identify the script's environment assumptions. On a macOS host, build the aarch64 and x86_64 targets and use lipo -info <binary> to check the artifact's slices. Record whether universal2 is feasible; the issue says no macOS host is currently available.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

documentation release

T27 row: T27-42
Work package: RP-03 — macOS packaging and notarization
Priority: P1
Status: NOT STARTED

Objective

Audit the macOS packaging script and establish that both Apple Silicon and Intel binaries build, and decide whether a universal2 artifact is achievable.

Acceptance criteria: The script is audited and its environment assumptions recorded; aarch64 and x86_64 targets both build; universal2 feasibility is decided and written; lipo -info confirms the slices actually present in the artifact.

Inputs

packaging/build-macos-dmg.sh; docs/TOOLCHAINS.md; a macOS host with Xcode CLT; lipo.

Authority

docs/RELEASE-ENGINEERING-PLAN.md §3.3 (macOS requirements, including the audit and the both-architecture verification).

Stopping condition

Both slices are built and verified, and the universal2 decision is recorded.

Verification

lipo -info <binary>

Evidence and blockers

Recipe-only; never built. The 2026-11-06 fleet cross-build (GNU) is preview evidence and does not establish the macOS toolchain story.

The artifact-build half of this row — both architectures producing a launchable artifact — is carried by issue #31 (board row T27-36/T27-37 covers the Windows/macOS build receipts); what remains specific to this row is the audit of packaging/build-macos-dmg.sh, the two-target build (aarch64 and x86_64), the universal2 feasibility decision, and the lipo -info confirmation of the slices actually present.

Blocker: no macOS host.


Ledger: docs/tasks/T27-42-macos-architectures.md and docs/release/EXECUTION-BOARD.md row T27-42 (these land with PR #12).
Campaign: docs/planning/release-compaign/Cross-Platform Releas.txt.

Lenguaje dominante
Rust
Estrellas
11
Forks
1
Merge medio
9 h 48 min
PR fusionados (30 d)
13

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de aliasfoxkde/FireCraft

Todos los issues de aliasfoxkde/FireCraft

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.