On 08.03.2012 09:08, Mladen Turk wrote:
On 03/08/2012 09:02 AM, rj...@apache.org wrote:
Author: rjung
Date: Thu Mar 8 08:02:45 2012
New Revision: 1298288
URL: http://svn.apache.org/viewvc?rev=1298288&view=rev
Log:
Remove "--force" from libtoolize in buildconf
to prevent overwrite of our config.(guess|sub)
copies with system installed ones.
Think that doesn't cause to overwrite config files only libtool ones.
I'm pretty sure it does overwrite them and that's why I removed it from
APR buildconf long ago, because we always shipped APR with outdated
config file although file in SVN was more recent (until I fixed it).
Actually might be even desired to have such feature if user
wishes to re-run buildconf
By "feature" you mean overwriting our config.* files? A user can re-run
buildconf (as we do), the question is whether bundled files should have
preference. I think yes, because most platforms are totally out of date.
If a user wants to provide a newer file, he can directly overwrite our
bundled ones.
But maybe I misunderstood you.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
