On 2020-07-02 13:08, Peter Robinson wrote:
I suppose "very good state" is a relative term, upstream hasn't seen a release since 2016 so is essentially "unmaintained", not sure it supports secure boot, probably has a bunch of CVEs (see point about maintenance). I think it only lives on in Fedora is because I think it's used for some (.iso?) install method, AFIACT it's eventually glued back together when it fails to build and is generally ignored.
As "very good state" I meant that the subpackages contain everything needed, and the binaries work flawlessly for the above use cases. Before, in some cases I was forced to use binaries from the upstream tarball.
I started to collect the sources (the upstream repo, various branches like [1]), Fedora patchset, the "dist-gits" from other distributions listed in Repology [2], bug trackers), and will try to give more informed answer to your questions once I manage to asemble something ala src-git with pair of branches (patches/applied) per distribution.
Kind Regards, Alek [1] https://github.com/awalls-cx18/syslinux/commits/master [2] https://repology.org/project/syslinux/versions _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
