[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v4 10/15] autoconf: update m4/pkg.m4

On Tue, 2014-04-29 at 18:12 -0700, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@xxxxxxxx>
> The provenance of the m4 pkg.m4 macro library was not documented
> and it was not clear how and if we can update this without breaking
> things. Document where this comes from, update us to the latest
> release from git and put a warning about avoiding private evolutions
> so that instead things go upstream.
> The pkg-config m4 macro library comes from the upstream pkg-config
> git repository [0]. If you update the m4 library update this file
> with provenance and last commit ID information. For documentation
> on how to use this read the pkg-config(1) man page.
> Tree: git://anongit.freedesktop.org/pkg-config
> The last synch was from commit:
> commit 4f0084d9d3b8726a797a373c7ec5e406000995d0
> Author: Dan Nicholson <dbn.lists@xxxxxxxxx>
> Date:   Mon Feb 3 15:59:18 2014 -0800
>     glib: Fix Makefiles to suppress warnings from automake
>     With the newly added glib.mk, some of the noinst_* variables need to use
>     += in the evaluation to avoid multiple definition warnings from
>     automake.
> Cc: Ian Campbell <ian.campbell@xxxxxxxxxx>
> Cc: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
> Cc: Jan Beulich <jbeulich@xxxxxxxx>
> Cc: Keir Fraser <keir@xxxxxxx>
> Cc: Tim Deegan <tim@xxxxxxx>
> Signed-off-by: Luis R. Rodriguez <mcgrof@xxxxxxxx>

Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

> ---

Please note here (after the --- marker) if the committer should rerun

> diff --git a/m4/pkg.m4.README b/m4/pkg.m4.README

Since it seems like the advice here could apply to multiple modules I
wonder if we should start off with m4/README.source or some such and a
list of the relevant upstreams (a list of 1 entry now, I don't expect
you to reverse engineer the others)?

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.