On Fri, Sep 20, 2019 at 03:12:01PM +0100, Daniel P. Berrangé wrote:
> There are various ideas / plans floating around for future libvirt work,
> some of which is actively in progress. Historically we've never captured
> this kind of information anywhere, except in mailing list discussions.
> In particular guidelines in hacking.html.in don't appear until a policy
> is actively applied.
> 
> This patch attempts to fill the documentation gap, by creating a new
> "strategy" page which outlines the general vision for some notable
> future changes. The key thing to note is that none of the stuff on this
> page is guaranteed, plans may change as new information arises. IOW this
> is a "best guess" as to the desired future.
> 
> This doc has focused on three areas, related to the topic of language
> usage / consolidation
> 
>  - Use of non-C languages for the library, daemons or helper tools
>  - Replacement of autotools with meson
>  - Use of RST and Sphinx for documentation (website + man pages)
> 
> Signed-off-by: Daniel P. Berrangé <berra...@redhat.com>
> ---
>  docs/docs.html.in     |   3 +
>  docs/strategy.html.in | 143 ++++++++++++++++++++++++++++++++++++++++++
>  2 files changed, 146 insertions(+)
>  create mode 100644 docs/strategy.html.in

[...]

> +    <p>
> +      The meson build system is written in Python, at time of writing,
> +      requiring version 3.4 or later. This directly informs the choice to use
> +      Python 3.4 as the language for all supporting build scripts, 
> re-inforcing
> +      the other benefits of Python, over Perl, Shell, M4, automake, etc.
> +    </p>

In addition to all comments, Meson since version 0.45.0 requires
Python 3.5 and we will most likely use at least 0.49.0.

Pavel

Attachment: signature.asc
Description: PGP signature

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Reply via email to