From: John Leuner <jewel@pixie.co.za>
To: mauve-discuss@sources.redhat.com
Subject: Re: Configure weirdness
Date: Mon, 18 Aug 2003 17:20:00 -0000 [thread overview]
Message-ID: <1061225035.414.31.camel@cmalu> (raw)
In-Reply-To: <200308151520.h7FFKHwr024599@piglet.dstc.edu.au>
I'm also in favour of redoing the build system for mauve. The project
needs to be a little easier to use for new users (and for maintainers
too).
John Leuner
On Fri, 2003-08-15 at 16:20, Stephen Crawley wrote:
> Mark Wielaard <mark@klomp.org> wrote:
> > On Fri, 2003-08-15 at 14:49, Andrew Haley wrote:
> > > Out of interest, what versions of aclocal, automake, and
> > > autoconf work with Mauve for you?
> >
> > I am using:
> > automake 1.7.6
> > autoconf 2.57
>
> ... and I'm using automake 1.6.1 and autoconf 2.53 with no problems.
>
> I agree that getting rid of Mauve's dependency on automake / autoconf
> would be a good idea.
>
> -- Steve
>
>
>
>
> -- Steve
--
John Leuner <jewel@pixie.co.za>
prev parent reply other threads:[~2003-08-18 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 10:26 Andrew Haley
2003-08-15 11:36 ` Mark Wielaard
2003-08-15 12:51 ` Andrew Haley
2003-08-15 14:13 ` Mark Wielaard
2003-08-15 15:21 ` Stephen Crawley
2003-08-18 17:20 ` John Leuner [this message]
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=1061225035.414.31.camel@cmalu \
--to=jewel@pixie.co.za \
--cc=mauve-discuss@sources.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 read-only IMAP folder(s) and NNTP newsgroup(s).