On 04/27/2012 11:02 AM, Daniel P. Berrange wrote:
On Fri, Apr 27, 2012 at 12:59:45PM -0400, Cole Robinson wrote:
> Since for stable releases, some test files were over the 99 char
> limit for traditional tar filenames.
>
> Suggested by Osier here:
>
https://www.redhat.com/archives/libvir-list/2012-April/msg01435.html
>
> Signed-off-by: Cole Robinson <crobinso(a)redhat.com>
> ---
> configure.ac | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/configure.ac b/configure.ac
> index 89fe818..a819898 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -9,7 +9,7 @@ AC_CONFIG_AUX_DIR([build-aux])
> AC_CONFIG_HEADERS([config.h])
> AC_CONFIG_MACRO_DIR([m4])
> dnl Make automake keep quiet about wildcards & other GNUmake-isms
> -AM_INIT_AUTOMAKE([-Wno-portability])
> +AM_INIT_AUTOMAKE([-Wno-portability tar-ustar])
> AM_MAINTAINER_MODE([enable])
>
> # Maintainer note - comment this line out if you plan to rerun
IIRC we have discussed this before and one of the issues was that the
format is not nearly as portable. On the other hand, any system new
enough to have virtualization support ought to be new enough to be
able to have support for it.
I concur - no one is complaining about building libvirt on a machine
that lacks a reasonable tar (and if they DO complain, then we can worry
about what to do at that point).
ACK.
--
Eric Blake eblake(a)redhat.com +1-919-301-3266
Libvirt virtualization library
http://libvirt.org