From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [PATCH 0/3] cogito spec file updates Date: Wed, 04 May 2005 08:01:54 -0700 Message-ID: <4278E3E2.3010001@zytor.com> References: <200505041454.j44Eslpg004032@laptop11.inf.utfsm.cl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Petr Baudis , Chris Wright , Mark Allen , git@vger.kernel.org X-From: git-owner@vger.kernel.org Wed May 04 16:57:44 2005 Return-path: Received: from vger.kernel.org ([12.107.209.244]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DTLIA-00061j-A8 for gcvg-git@gmane.org; Wed, 04 May 2005 16:56:02 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261838AbVEDPC0 (ORCPT ); Wed, 4 May 2005 11:02:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261856AbVEDPC0 (ORCPT ); Wed, 4 May 2005 11:02:26 -0400 Received: from terminus.zytor.com ([209.128.68.124]:2452 "EHLO terminus.zytor.com") by vger.kernel.org with ESMTP id S261838AbVEDPCW (ORCPT ); Wed, 4 May 2005 11:02:22 -0400 Received: from [10.4.1.13] (yardgnome.orionmulti.com [209.128.68.65]) (authenticated bits=0) by terminus.zytor.com (8.13.1/8.13.1) with ESMTP id j44F1xlE025102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 4 May 2005 08:01:59 -0700 User-Agent: Mozilla Thunderbird 1.0.2-1.3.2 (X11/20050324) X-Accept-Language: en-us, en To: Horst von Brand In-Reply-To: <200505041454.j44Eslpg004032@laptop11.inf.utfsm.cl> X-Virus-Scanned: ClamAV version 0.84, clamav-milter version 0.84e on localhost X-Virus-Status: Clean X-Spam-Status: No, score=-3.5 required=5.0 tests=ALL_TRUSTED,AWL autolearn=ham version=3.0.3 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on terminus.zytor.com Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Horst von Brand wrote: > "H. Peter Anvin" said: > >>Petr Baudis wrote: >> >>>I wouldn't accept this neither. If git.spec is already version >>>controlled, it should be up-to-date in the version control. Therefore, >>>you need to update it at the time of release, not at the time of >>>generating the tarball. > > >>What I usually do is to have a *.spec.in file, and have my release >>script generate the *.spec file. I usually have a "version" file >>checked into the SCM from which all version information derives, >>including what to put in the *.spec file as well as what to name the >>subdirectory. > > Right. Note that this is /not/ autoconfiguring .spec from .spec.in, you are > "just" automating the process I do by hand. Right, the .spec.in here doesn't imply the use of autoconf. (That being said, if you *are* using autoconf, the "make release" target is also a good place to produce the autoconf generated files, being just another class of autogenerated-but-should-be-in-the-tarball files.) -hpa