th0ma7 changed the title cross+spk/ffmpeg{4,5,6}: mark BROKEN to drop them from the build spk/ffmpeg{4,5,6}: disable via DISABLED (also accept DISABLED as an alias for BROKEN)

ffmpeg 4.x / 5.x / 6.x are no longer part of the maintained build set: no
new ffmpeg4/5/6 SPK release is planned at this time, and disabling the SPK
keeps their large codec dependency trees out of the build.
Packages are disabled at the spk level (the CI package filter in
.github/actions/prepare.sh only looks at spk/*/), so a DISABLED file is
added to spk/ffmpeg{4,5,6}. To let the intent read clearly, the framework
now accepts either a BROKEN or a DISABLED file with the same effect -
both spksrc.rules/pre-check.mk and the CI prepare step honour either name,
and the package-lifecycle doc is updated accordingly.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

th0ma7 added a commit to th0ma7/spksrc that referenced this pull request

These were disabled in SynoCommunity#7283 to keep their large codec dependency trees out of the
build while no new releases were planned. With ffmpeg4/5/6 now declaring their gcc
floors (4.6.4 for the legacy-ARMv5 ffmpeg4, 4.9 for 5/6) and building against the
gcc8 overlay where needed, re-enable them by dropping the DISABLED markers.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QEH1b4ASNYSrZFQnEeroj8

6 tasks

hgy59 added a commit that referenced this pull request

- skip DISABLED packages
- with introduction of DISABLED packages in #7283, "make spk-clean" did not work anymore