From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff King Subject: Re: Chicken/egg problem building from a 'git clone' Date: Thu, 5 Mar 2009 07:06:02 -0500 Message-ID: <20090305120602.GA18717@coredump.intra.peff.net> References: <49AF9601.9060709@op5.se> <43d8ce650903050337n48924fc3l89ef991d578f5849@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: Git Mailing List To: John Tapsell X-From: git-owner@vger.kernel.org Thu Mar 05 13:07:44 2009 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1LfCMY-0004oZ-Go for gcvg-git-2@gmane.org; Thu, 05 Mar 2009 13:07:42 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751845AbZCEMGM (ORCPT ); Thu, 5 Mar 2009 07:06:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751774AbZCEMGM (ORCPT ); Thu, 5 Mar 2009 07:06:12 -0500 Received: from peff.net ([208.65.91.99]:41630 "EHLO peff.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751593AbZCEMGM (ORCPT ); Thu, 5 Mar 2009 07:06:12 -0500 Received: (qmail 30583 invoked by uid 107); 5 Mar 2009 12:06:11 -0000 Received: from coredump.intra.peff.net (HELO coredump.intra.peff.net) (10.0.0.2) by peff.net (qpsmtpd/0.40) with (AES128-SHA encrypted) SMTP; Thu, 05 Mar 2009 07:06:11 -0500 Received: by coredump.intra.peff.net (sSMTP sendmail emulation); Thu, 05 Mar 2009 07:06:02 -0500 Content-Disposition: inline In-Reply-To: <43d8ce650903050337n48924fc3l89ef991d578f5849@mail.gmail.com> Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Thu, Mar 05, 2009 at 11:37:45AM +0000, John Tapsell wrote: > > ./configure is a generated script. Including it in the repository is not > > something many projects do, since one of the things developers will be > > working on is to change how that file is generated. Including it in the > > release tar-balls is something every project (that uses autoconf) does, > > since those are aimed at end-users. > > Reason that it should be included: > > * configure scripts usually are included. git was the first source > code in a long time that I've seen without one I think you are confusing "checked into version control" with "distributed with release tarballs". Most projects do not do the former[1], but almost all (including git) do the latter. This discussion is about things checked into the repository. [1] Sorry, I don't have exact numbers, but I have never encountered this before. > * we have lots other files in git.git that are autogenerated (the > documentation files, for example) I'm not aware of any auto-generated files that are checked in. Can you give an example? > * people are used to being able to do "./configure; make; make install" Right. They do it from the release tarball. Getting the version straight from source-control usually means you have to have autoconf if you want to run it. > * It doesn't hurt anyone to do it. Yes, it does. Having generated files in your source repository means: - you generate useless noise commits when those files are re-autogenerated - developers must make sure that they are not accidentally committing auto-generated cruft that have nothing to do with their actual changes -Peff