I was mostly looking at this because I was worried by the complexity
(this doesn't involve emergency shell and similar yet... but if the plan
is to remove fbcon then at some point this means kmscon should work in a
semi-borked system, and I'm not convinced it would)

But this also bothered me, so heads up to save others a bit of time to
research.
The change (probably very rightfully) claims:
> '''fbcon''' is a terminal emulator in the kernel, which is not well
> maintained

Then I looked for kmscon... And found the fdo unmaintained original code:
https://www.freedesktop.org/wiki/Software/kmscon/

Then the fork that seems to be used:
https://github.com/Aetf/kmscon/issues/81

So basically this was unmaintained for years, then someone forked it and
also left it unmaintained for years, then Jocelyn came around and just
started taking over (okay, that comment is now 5 months old, but that's
yesterday as far as distro lifecycles go)

(this also depends on https://github.com/Aetf/libtsm which had a similar
fate)

While I appreciate the enthusiasm, and given I assume Jocelyn is doing
this on their work time I assume redhat will ensure project continuity
if required, I think it's worth a word in the change proposal.
(this doesn't meant I think it should be refused, I don't care much
either way and it's easy to revert in its current form... I'll want to
look much more closely at the early console/emergency setup once that's
working though)


Thanks,
-- 
Dominique Martinet | Asmadeus
-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to