Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

superplayer-moq ships one ABI from a locally built artifact: what publishing it would need

Aperta
  • Qualcosa non va?
#369 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
8/100
Tipo di issue
Documentazione
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
android, kotlin
Ambito
build-system, mobile

Direzione di ricerca

This is a tracking note, not a task: it records why the Phase 14 MoQ module stays out of the published set. Relevant files are settings.gradle.kts (the published set), docs/compatibility.md (the stability table, checked by verifyCompatibilityDocument), THIRD_PARTY.md and CONTRIBUTING.md (the dependency policy). Done means a maintainer decision on the licence and build-matrix conditions, not a code change.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

question

What this is

A tracked limit, not a ticket to pick up. Phase 14's MoQ module links a locally built
moq-ffi for arm64-v8a only, and is deliberately excluded from the published set (#351,
#364). This issue is where what shipping would actually need is written down, so that "unpublished"
stays a decision rather than becoming an oversight.

What is missing

  • armeabi-v7a and x86_64 are unbuilt and untested. #351 built arm64 alone because this host
    is Apple Silicon and its only system image is arm64. Upstream ships all three.
  • No Intel-host emulator can run this, which narrows who can reproduce a Phase 14 result.
  • The artifact is not reproducible by a consumer. It is built from a source checkout with
    --no-default-features, which is what subtracts the MPL-2.0 decoder crates from the graph
    (#351). The Maven artifact a consumer would resolve does not carry that subtraction, so
    publishing this module against the upstream coordinate would reintroduce exactly the licence
    problem #351 closed.

That last point is the real content here. The ABI gap is a build-matrix problem; the licence gap is
a policy problem, and it is the one that decides whether this module can ever publish.

What would have to be true to publish

  • A reproducible build of moq-ffi with default features off, for every ABI the library targets,
    produced by something other than one developer's machine.
  • Either an upstream change that makes the decoder feature opt-in rather than default, or a
    published artifact of our own with its provenance stated — at which point THIRD_PARTY.md and
    CONTRIBUTING.md's dependency policy are both back in scope.
  • docs/compatibility.md's stability table and settings.gradle.kts' published set agree on the
    module's presence, which verifyCompatibilityDocument checks as a set.

Proposing the feature change upstream is adjacent to #354 and carries no work in this repository.

Blocked by

Nothing. This blocks nothing in Phase 14 either; the phase's exit criterion is a broadcast playing
on a device, and an unpublished module satisfies it.

Lingua principale
Kotlin
Stelle
1
Fork
0
Merge medio
1h 20m
PR unite (30g)
172

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ramesh130/superplayer

Tutte le issue di ramesh130/superplayer

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.