From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>,
edk2-devel-01 <edk2-devel@ml01.01.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
"afish@apple.com" <afish@apple.com>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [Bug 164] Add the build option "/D DISABLE_NEW_DEPRECATED_INTERFACES" in package DSC files
Date: Fri, 21 Oct 2016 21:19:12 +0100 [thread overview]
Message-ID: <CAKv+Gu_EPh4oueyzPFRJNjZYj7F1DSQ_ukVWtbzj1iK1kmandQ@mail.gmail.com> (raw)
In-Reply-To: <da6e08cc-1c4d-4d75-c54a-4ac552b4dce9@redhat.com>
On 21 October 2016 at 21:14, Laszlo Ersek <lersek@redhat.com> wrote:
> On 10/21/16 21:58, Jordan Justen wrote:
>> On 2016-10-21 12:37:21, Ard Biesheuvel wrote:
>>> I don't remember seeing any discussion regarding
>>> DISABLE_NEW_DEPRECATED_INTERFACES on the list, so I am a bit surprised
>>> seeing these bugs being filed and assigned.
>>>
>>
>> I agree.
>>
>> Also, the terminology seems confusing. 'new deprecated' seems like a
>> contradiction. I guess it means 'newly deprecated', but that seems
>> like a term that is quickly going to become obsolete. Soon there will
>> be old deprecated items that are disabled with this switch.
>> DISABLE_DEPRECATED_INTERFACES sounds better.
>>
>> But, shouldn't we have platforms opt-in to using the deprecated
>> interfaces rather than adding DISABLE_NEW_DEPRECATED_INTERFACES to the
>> build command line for every EDK II platform?
>>
>> Not using deprecated items should be the default for EDK II platforms.
>> If a platform has to opt-in to the deprecated content in their .dsc,
>> then it is obvious that they are relying on deprecated functionality.
>>
>> So, I guess I'd propose adding ENABLE_DEPRECATED_INTERFACES instead.
>
> I'm about to post a ~20-part series for OvmfPkg and ArmVirtPkg together
> that solves these BZs. :/ The DISABLE_NEW_DEPRECATED_INTERFACES feature
> test macro is already being used in three MdePkg library class header
> files (and a number of library instances), so I thought it was a done deal.
>
> I don't want to stifle the discussion of course, but at this point I
> think I will post the patches for review.
>
Yes, please. Removing uses of deprecated interfaces is something we
should do anyway. What we shouldn't do is configure our platforms in
such a way that additional future deprecation automatically break the
build, unless we have a strong commitment from the other package
owners that they will ensure that this does not happen.
next prev parent reply other threads:[~2016-10-21 20:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-164-63@https.bugzilla.tianocore.org/>
[not found] ` <bug-164-63-L8k0GFC2io@https.bugzilla.tianocore.org/>
2016-10-21 19:37 ` [Bug 164] Add the build option "/D DISABLE_NEW_DEPRECATED_INTERFACES" in package DSC files Ard Biesheuvel
2016-10-21 19:41 ` Michael Zimmermann
2016-10-21 19:58 ` Jordan Justen
2016-10-21 20:14 ` Laszlo Ersek
2016-10-21 20:19 ` Ard Biesheuvel [this message]
2016-10-21 20:40 ` Laszlo Ersek
2016-10-21 20:57 ` Ard Biesheuvel
2016-10-21 20:20 ` Andrew Fish
2016-10-21 20:39 ` Jordan Justen
2016-10-21 20:54 ` Andrew Fish
2016-10-21 20:55 ` Andrew Fish
2016-10-21 21:02 ` Laszlo Ersek
2016-10-21 22:10 ` Jordan Justen
2016-10-21 22:31 ` Laszlo Ersek
2016-10-21 23:13 ` Yao, Jiewen
2016-10-23 14:28 ` Mudusuru, Giri P
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKv+Gu_EPh4oueyzPFRJNjZYj7F1DSQ_ukVWtbzj1iK1kmandQ@mail.gmail.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox