Hello Jürgen, I agree with you and I'm certainly one of those people who find these files to be very useful. I believe your message was probably intended for Robin?
Regards, Elias On 27 January 2014 19:55, Juergen Sauermann <[email protected]>wrote: > Hi Elias, > > actually what you see in the SVN repository is what "make dist" thinks > should be distributed. > It is exactly the files in the apl-1.X.tar.gz (and possibly some stale > ones if I forgot to remove them). > > The thing with auto-generated files is that there are two steps: > autoreconf and ./configure. > > If I would remove all generated files (which would include all .in files) > then the user > would need autoconf (and most likely the proper version of it) to be > installed. > I believe "make dist" wanted to avoid that. > > I guess the merge conflicts can be avoided by "make distclean" before "svn > up". > > /// Jürgen > > > > On 01/27/2014 10:18 AM, Elias Mårtenson wrote: > > * You should not commit generated files (autotools) into the SVN > >> repository. Everyone who has to regenerate the autotools files for >> one reason or another is left with dozens of locally changed files >> and will face merge conflicts if you choose to commit your version >> of auto-generated files. >> I suggest removing all auto-generated files from the >> repository and setting the svn:ignore property on the parent >> directories to ignore these files instead. When you create source >> tar-balls with "make dist", automake is smart enough to include >> some of the auto-generated files like "configure" automatically. >> > > This is just my opinion, but I'm very glad that these files are > committed into the repository. This is because getting a fully working > autoconf environment is ridiculously hard. I'm running two different Linux > distributions (Ubuntu and Arch) as well as OSX on my machines, and not a > single one of them can successfully run autoconf on this (and many others) > project. > > Regards, > Elias > > >
