Configure weirdness

Configure weirdness

[Andrew Haley]

I note that "configure" is still missing from Mauve, despite the fact
that the instructions tell you to run it!

As far as I'm aware, this is the only free software project that
requires its users (as opposed to maintainers) to run automake and
autoconf.  This, of course, means that the users have a dependency not
only on automake and autoconf, but on particular versions of there
tools.  We gain nothing by having these files absent.

Let's put them back.

Andrew.

Re: Configure weirdness

[Mark Wielaard]

Hi,

On Fri, 2003-08-15 at 12:25, Andrew Haley wrote:
> I note that "configure" is still missing from Mauve, despite the fact
> that the instructions tell you to run it!

OK. I failed to update the instructions and/or actually make a released
version of mauve that does contain these files. I give up my resistance.

> As far as I'm aware, this is the only free software project that
> requires its users (as opposed to maintainers) to run automake and
> autoconf.

My idea was to create an actual mauve release for users that contained
generated files. And have the CVS version only for maintainers, but
clearly users also use the CVS version. (Actually I want to get rid of
the auto* tools for Mauve since I think the only function they now have
is to find out the /tmp dir location and the file separator char. It
seems they are more trouble then they are worth for this project.) 

>   This, of course, means that the users have a dependency not
> only on automake and autoconf, but on particular versions of there
> tools.  We gain nothing by having these files absent.
> 
> Let's put them back.

If nobody objects I suggest you check them in. But then we have to be
careful to always check in an up to date version. They were removed in
the first place because they are generated files that were not always
updated correctly which also causes trouble for both users and
maintainers.

Cheers,

Mark

Re: Configure weirdness

[Andrew Haley]

Mark Wielaard writes:
 > > 
 > > Let's put them back.
 > 
 > If nobody objects I suggest you check them in. But then we have to be
 > careful to always check in an up to date version.

Sure.  Out of interest, what versions of aclocal, automake, and
autoconf work with Mauve for you?

Andrew.

Re: Configure weirdness

[Mark Wielaard]

Hi,

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

Cheers,

Mark

Re: Configure weirdness

[Stephen Crawley]

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

Re: Configure weirdness

[John Leuner]

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>