After reviewing the options, I believe #1 is the best approach. The deblob scripts eventually won't exist as we move to a different method, so relying on them isn't maintainable long-term and will likely affect Trisquel's process as well.
Currently, the freesh sources are at https://linux-libre.fsfla.org/pub/linux-libre/freesh/. The .deb files are generated using a modified version of the kernel's own build scripts (found in scripts/package) via make bindeb-pkg at compile time, but this isn’t ideal for producing distro-quality packages. It's likely more sustainable to reuse Debian's kernel packaging instead so that Linux-libre on debian incorporates the same configs, patches, etc. https://salsa.debian.org/kernel-team/linux Additionally, the same security patches applied to Debian's version of Linux should apply to Linux-libre. If the main security team doesn't want to cover this as indicates, perhaps someone else could do that? I expect most patches would apply as-is.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ linux-libre mailing list [email protected] http://www.fsfla.org/cgi-bin/mailman/listinfo/linux-libre
