Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 25 Oct 2001 09:06:19 -0700
From:      "David O'Brien" <obrien@FreeBSD.org>
To:        Mario Sergio Fujikawa Ferreira <lioux@uol.com.br>
Cc:        Maxim Sobolev <sobomax@FreeBSD.org>, John Baldwin <jhb@FreeBSD.org>, cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org
Subject:   Re: cvs commit: ports/devel/automake Makefile distinfo pkg-plist
Message-ID:  <20011025090619.B29809@dragon.nuxi.com>
In-Reply-To: <20011025135404.A2336@exxodus.fedaykin.here>; from lioux@uol.com.br on Thu, Oct 25, 2001 at 01:54:04PM -0200
References:  <XFMail.011024143149.jhb@FreeBSD.org> <3BD7C115.63F75C69@FreeBSD.org> <20011025081956.G28706@dragon.nuxi.com> <20011025135404.A2336@exxodus.fedaykin.here>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 25, 2001 at 01:54:04PM -0200, Mario Sergio Fujikawa Ferreira wrote:
> 	1) for some reason, the distfile (not the port) USES auto{conf,make}
> during configure/build process. Some developers want to do things
> dynamically

This can often be fixed with "touch configure Makefile.in".
I do this in the GCC ports.  There is a small race condition when
Makefile.am and Makefile.in have the same date (and Makefile.in is still
up to date).

> 	2) patching *.in *.am files sometimes is CLEANER, easier to
> understand and (of course) smaller than patching .in files.

In all the 135 ports I've maintained I've never seen that.  Can you
please expand?

> Furthermore, sometimes it is not possible to patch Makefile.in files,
> since they might get re-generated during build (check (1))

See my response to (1).

-- 
-- David  (obrien@FreeBSD.org)

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011025090619.B29809>