Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 12 Jan 2019 12:26:33 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 234833] USES=autoreconf fails if a port uses gettext but user disables NLS port option
Message-ID:  <bug-234833-7788-goWXbr7kIt@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-234833-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-234833-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234833

--- Comment #9 from Tijl Coosemans <tijl@FreeBSD.org> ---
Sigh...  So, you suggest running only autoconf, because you only modify
configure.ac.  Makes sense right?  But it's wrong!  And in the case of
fetchmail autoconf itself warns about that because aclocal.m4 was generated=
 for
autoconf 2.68 while the ports tree runs 2.69.

The fetchmail Makefile also lets aclocal.m4 depend on configure.ac, which m=
eans
make will try to run aclocal during build, and fail since, because you only=
 ran
autoconf, it will look for aclocal-1.11 while the ports tree has 1.16.  Then
configure depends on aclocal.m4 so make will rerun autoconf.  Furthermore,
Makefile.in depends on configure.ac so it will run automake as well, and fa=
il
again because of a version mismatch.  Makefile depends on config.status whi=
ch
depends on configure so make will rerun configure but without CONFIGURE_ENV=
 and
because configure got regenerated it will not have any of the modifications
(current+future!) that the ports infrastructure applies to it.  You could of
course pile on more hacks to work around these things...

I'm afraid you are only looking at this from the perspective of a single po=
rt.=20
Portmgr has to check every change against 30000+ ports.  For a single port
hacks are maintainable.  For 30000+ ports they are not.  Hacks are ineffici=
ent
at that scale.  They break way too often.  If adding a build dependency
eliminates hacks and is more likely to keep build scripts in the work direc=
tory
in a consistent state then we add the build dependency.  If you look at how
much easier post-USES=3Dautoreconf autotools updates are compared to the
USE_AUTOTOOLS days then this approach is clearly the right one.  If you sti=
ll
insist on keeping hacks I reserve the right to mark the port broken if it e=
ver
fails to build in an exp-run.

Please just add USES=3Dgettext-tools and move on to something more importan=
t.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234833-7788-goWXbr7kIt>