Date: Thu, 25 Oct 2001 00:24:26 EEST From: Maxim Sobolev <sobomax@FreeBSD.org> To: fenner@research.att.com Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/devel/automake Makefile distinfo pkg-plist ports/devel/automake/files patch-ab patch-ad Message-ID: <200110242124.AAA99755@ipcard.iptcom.net> In-Reply-To: <200110242110.OAA09404@windsor.research.att.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 24 Oct 2001 14:10:01 -0700, Bill Fenner wrote: > > >2. Pre-create Makefile.in/configure with the whatever version of > > autocrap you favorite port requires and then add those files > > as patches in the FILESDIR or PATCHFILE at the MASTER_SITE_LOCAL. > > I thought the usual reason for using autoconf at port build time was > to avoid having large configure diffs (i.e. just patch configure.in > and then run autoconf, instead of patching configure.in and then > also configure, with all the line number changes etc.) Not actually. I believe that mojority of USE_AUTOMAKE/USE_AUTOCONF ports use that just because the vendor due to some unclear reasons supplied distfile without configure and/or Makefile.in scripts. Patching configure instead of configure.in isn't much more difficult task, in fact it may even be simpler, because you are dealing with the straight sh script, not with something that will then be preprocessed into radically different format. -Maxim 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?200110242124.AAA99755>