From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [RFC] Proposal to align autotool versions
Date: Tue, 24 Nov 2009 14:33:58 +0100 [thread overview]
Message-ID: <4B0BE0C6.4000702@redhat.com> (raw)
Hi guys,
I just completed testing of autotools in F13/rawhide and they seem to
fulfill perfectly what we need so far.
Fedora13 has:
libtool 2.2.6 (doesn?t carry the bug for which we were forcing 2.2.7)
autoconf 2.64 (higher than what we require now)
automake 1.11/m4/pkg-config in more than recent enough versions.
corosync/openais will eventually get libtool support.
cluster-stable3 autotool implementation is eventually on the schedule.
cluster/master trees are already ported.
My suggestion is simply to use those versions across the projects so
that developers will not require any longer to manually build autotools
and can start easily testing again master trees.
Please ACK/NACK.
Fabio
next reply other threads:[~2009-11-24 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 13:33 Fabio M. Di Nitto [this message]
2009-11-24 13:38 ` [Cluster-devel] [RFC] Proposal to align autotool versions Steven Whitehouse
2009-11-24 16:12 ` [Cluster-devel] Re: [Openais] " Steven Dake
2009-11-24 16:24 ` Fabio M. Di Nitto
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-all 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=4B0BE0C6.4000702@redhat.com \
--to=fdinitto@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).