linux-ext4 - Re: Generated files in e2fsprogs git repo

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140701010250.GA23932@thunk.org>
Date:	Mon, 30 Jun 2014 21:02:50 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	"Burton, Ross" <ross.burton@...el.com>
Cc:	linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Re: Generated files in e2fsprogs git repo

On Mon, Jun 30, 2014 at 05:52:29PM +0100, Burton, Ross wrote:
> 
> Would anyone object to a patch set to remove all generated files
> (aclocal.m4, configure, intl/*, po/Makefile.in.in, etc) from the
> e2fsprogs git repository?  They'll still exist in tarballs, but anyone
> building from git would need to run autoreconf to regenerate them -
> the plus side being that the shipped aclocal.m4 won't be forcing
> archaic macros onto users.

I don't trust autoreconf.  Different versions of autoconf can end up
with different incompatible versions of autoconf macros, and I have
seen some rather disastrous failures as a result.  That's why I update
autoconf under my control, and if you run autoreconf as a user, and it
breaks because the "archaic macros" work, and the "new shiny" macros
fail, that's your problem, and I will laugh at you....

      	     	  	       	      - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html