On 10/22/16 00:10, Jordan Justen wrote: > On 2016-10-21 14:02:44, Laszlo Ersek wrote:
>> Honestly, I imagined that DISABLE_NEW_DEPRECATED_INTERFACES would be >> temporary in the edk2 tree. That is, it's a means so we can gradually >> transition with all the in-tree stuff to a deprecationless code base. >> Once that's done -- i.e., *all* platform DSCs within the edk2 tree >> specify this feature test macro under their respective [BuildOptions] >> sections --, then whatever the macro excises from the core packages can >> be removed permanently, together with those platform [BuildOptions]. >> > > That could be reasonable, although I'd argue that we could flip it > around. Opt-in to the deprecated interfaces on all platforms, and then > start marking deprecated interfaces. Finally we could clean up > platforms and removed the override. That's a valid idea, IMO. > But ... I think DISABLE_NEW_DEPRECATED_INTERFACES was first added in: > > commit bf4a3dbd4751b6411bdfc98bf3ac2c4f928bdfdf > Author: ydong10 <ydong10@6f19259b-4bc3-4df7-8a09-765794883524> > Date: Wed May 30 07:36:00 2012 +0000 > > So, I guess it is not going to be removed anytime soon. :( I believe we just need to make progress with the individual platforms (and their dependencies from other Pkgs). It's not a lot of fun, but the BZs exist (well, they can be filed) now, and then we can address them... I mean, I didn't care (or, really, know) about DISABLE_NEW_DEPRECATED_INTERFACES until the ArmVirtPkg / OvmfPkg BZs got filed. Bugzilla is great. I like the attention that it gets, from others and from myself. Thanks Laszlo _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
