On Wed, May 29, 2019 at 12:09:43PM +0200, Alexander Graf wrote:
Do you want to change this policy? (I'm just asking.)
I am using SCT a lot to test my patches. I want to be able to run the tests on the final code.
Wouldn't it be better to patch/fork the upstream SCT that blindly pulling in obsolete code that is basically already dead?
I have raised a ticket for upstream SCT but did not see any reaction up to now.
Got a reference to the ticket?
Making this deprecated protocol a config option deselected by default is the most plausible solution to me. In the Kconfig comment I made it clear that this protocol is going to be removed when the SCT has been corrected.
I disagree, I think if it's obsolete not having the code in the first case in the most plausible option IMO.
Since it's hidden behind a default-n config option, I'd not be terribly opposed to it. I do agree that fixing SCT is the better path forward.
Leif, how long do you think fixing this properly in SCT is going to take?
Well, as usual, patches welcome :)
However, I think the problem is more that the separate SCT area of bugzilla is a fairly recent addition and they forgot to change the default assignee to someone who actually works on SCT...
I have now added the SCT maintainers to cc on https://bugzilla.tianocore.org/show_bug.cgi?id=1802
/ Leif