On 05/02/2020 19.53, Aleksandar Markovic wrote: > On Wed, Feb 5, 2020 at 7:03 PM Aleksandar Markovic > <aleksandar.m.mail@xxxxxxxxx> wrote: >> >>> The deprecation policy is primarily intended for notifying of changes >>> to QEMU's stable interfaces ( CLI, HMP, QMP) which affect behaviour >>> and usage of QEMU at runtime & are liable to break apps managing >>> QEMU. >>> >>> Changes to build time options have no strong reason to be subjected to >>> the deprecation process. >> >> This sounds reasonable to me. >> >> But: Should our deprecation policy be clearer on what is subject to >> our deprecation procedure, and what is not? >> >> Regards, >> Aleksandar >> > > And, there is even a section devoted to the build system in > https://qemu.weilnetz.de/doc/qemu-doc.html#Deprecated-features : > > B.10 Build system > > B.10.1 Python 2 support (since 4.1.0) > > In the future, QEMU will require Python 3 to be available at build > time. Support for Python 2 in scripts shipped with QEMU is deprecated. > > The wording above comes from the file in our source tree: qemu-deprecated.texi . > > Shouldn't the cases like "--enable-blues" be documented here? I think > the deprecation of bluetooth devices support should have included a > short section on involved configure options here. > > Why is Python 2 support different to "--enable-blues" support? There > should not be some unknown and arbitrary criterium what do and what > doesn't come in this subsection. > > Or, if our build system is not subject to our deprecation policy, than > what is the entire subsection "B.10 Build system" doing here, in > section "Deprecated features"? See here: https://lists.gnu.org/archive/html/qemu-devel/2020-01/msg02552.html i.e. the section was here rather by "accident". It will be removed once my "qemu-deprecated: Remove text about Python 2" patch hits the master branch. Thomas
